mgetadmin/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-10-28 10:57:08 -04:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

Say how an update is actually run, and show the fork case first

Browse Source 
The update block told people to reach the container with pct, which is
not how anyone gets there; the website says to type "update" in the
container console, so say that. VM scripts have no updater at all, which
the page did not mention.

The fork example exported the core URL, which only matters when the
engine itself is being changed -- the ordinary case is a fork of the
scripts, and it needs COMMUNITY_SCRIPTS_URL or the engine looks for the
install half upstream. Neither needs exporting.
This commit is contained in:
MickLesk
2026-10-26 10:41:19 +01:00
parent a7f39fb710
commit 2d4b7b669b
1 changed files with 21 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
README.md
View File

@@ -60,16 +60,15 @@ finish in a few minutes.
**Advanced** hands you container settings, networking, storage backend and
application options before anything is created.
Every container gets an `update` command. Enter the container and run it to
update the installed application:
Every container gets an `update` command. Type it in the container console:
```bash
pct enter <ctid>
update
```
The same command reaches settings that would otherwise mean editing config files
by hand.
It updates the installed application and reaches settings that would otherwise
mean editing config files by hand. VM scripts have no built-in updater — use the
guest's own package manager.
---
@@ -115,15 +114,27 @@ request a change.
## Testing a fork or branch
Engine and scripts resolve independently, so either can point somewhere else:
Engine and scripts resolve independently, so either can point somewhere else.
Put the variable on the command itself — nothing needs exporting.
To run your own copy of the scripts:
```bash
export COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/YOU/core/my-branch
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)"
COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/YOU/ProxmoxVE/my-branch \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/YOU/ProxmoxVE/my-branch/ct/debian.sh)"
```
To run your own script repository instead, set `COMMUNITY_SCRIPTS_URL` the same
way. A local checkout of core wins over both — point at it with
A `ct/` script fetched with `curl` cannot tell the engine where it came from, so
without that variable it would look for its `install/` half upstream.
Only when you are changing the engine itself:
```bash
COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/YOU/core/my-branch \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)"
```
A local checkout of core wins over both — point at it with
`COMMUNITY_SCRIPTS_CORE_DIR`.
---