Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion DEPLOY.md
Original file line number Diff line number Diff line change
Expand Up @@ -379,10 +379,11 @@ If you rely on external sign-in, keep `TRAINING_HUB_ADMIN_USERNAMES` or `TRAININ

## 14) Regular Updates

Upload the changed release files, keep `.env.production`, then run:
`update.py` rebuilds and restarts whatever is checked out; it does not fetch new commits (its `--pull` only refreshes Docker base images). Pull the release first, keep `.env.production`, then run:

```bash
cd /srv/scamscreener
git pull --ff-only origin main

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep updates compatible with uploaded deployments

Section 7 instructs operators to upload repository contents and never requires /srv/scamscreener to be a Git checkout with an origin remote, so deployments created exactly as documented can fail here with “not a git repository.” When this multi-line block is pasted into an interactive shell, Bash still proceeds to update.py, rebuilding the stale tree and potentially reporting a successful update. Either make the initial installation explicitly clone/configure this repository or retain an upload-based update path and stop execution if release acquisition fails.

AGENTS.md reference: AGENTS.md:L121-L125

Useful? React with 👍 / 👎.

python3 scripts/update.py
```

Expand Down