Clarify public HTTPS for VPS vs SSH for developers
- VPS wget uses full gitea.dialer.work URL without auth for rubix-deploy - Document gitea SSH remote for pushes; token still required for private rubix zip
This commit is contained in:
@@ -2,8 +2,14 @@
|
||||
|
||||
Bootstrap **step 1** for new Rubix servers (install app from Gitea release).
|
||||
|
||||
**Repository:** https://gitea.dialer.work/swissdatabase/rubix-deploy
|
||||
**Clone:** `git clone https://gitea.dialer.work/swissdatabase/rubix-deploy.git`
|
||||
**Public repo (VPS / any client):** full HTTPS URLs — no SSH, no token for this script.
|
||||
|
||||
**Developers (your PC, `~/.ssh/config` alias):**
|
||||
|
||||
```bash
|
||||
git remote add gitea git@gitea.dialer.work:swissdatabase/rubix-deploy.git
|
||||
git push -u gitea main
|
||||
```
|
||||
|
||||
## On a new VPS
|
||||
|
||||
@@ -14,13 +20,8 @@ chmod +x install-rubix.sh
|
||||
sudo ./install-rubix.sh
|
||||
```
|
||||
|
||||
If the repo is **Internal** (not Public), use a token to fetch the script:
|
||||
`install-rubix.sh` still prompts for a **Gitea token** to download the private **rubix** release zip — only `rubix-deploy` is public.
|
||||
|
||||
```bash
|
||||
wget --header="Authorization: token <GITEA_TOKEN>" -O install-rubix.sh \
|
||||
https://gitea.dialer.work/swissdatabase/rubix-deploy/raw/branch/main/install-rubix.sh
|
||||
```
|
||||
|
||||
The script: `apt update` + `apt upgrade`, installs tools, asks for token, creates `/home/www/callcenter`, downloads **rubix**.
|
||||
The script: `apt update` + `apt upgrade`, installs tools, creates `/home/www/callcenter`, downloads **rubix**.
|
||||
|
||||
**Step 2+** (`.env`, Docker, `up.sh`): [swissdatabase/rubix](https://gitea.dialer.work/swissdatabase/rubix) README.
|
||||
|
||||
Reference in New Issue
Block a user