The site with guess which URL?
|
All checks were successful
Forgejo Runner CI / Build (self-hosted Forgejo runner) (push) Successful in 45s
|
||
|---|---|---|
| .github/workflows | ||
| public | ||
| scripts | ||
| src | ||
| .gitignore | ||
| eslint.config.js | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| vite.config.js | ||
socialist.live
A tiny React + Vite site that serves the socialist.live landing page. The repo also carries the CI configuration used by the self-hosted Forgejo runner that deploys the built assets to the server.
Local development
- Install dependencies:
npm install - Start the dev server:
npm run dev - Lint:
npm run lint - Build:
npm run build
Deployment
The workflow .github/workflows/forgejo-runner.yml installs dependencies, runs lint, builds, and deploys dist/:
- Local deploy (default): copies
dist/toDEPLOY_DIR(default/srv/www/socialist.live) on the runner. Requires the runner to have write access (orsudo). - Remote deploy (default): uses
SSH_DEPLOY_KEYand syncsdist/over SSH to${DEPLOY_USER:-aron}@${DEPLOY_HOST:-172.17.0.1}:${DEPLOY_DIR}(rsync excludesdata/to avoid clobbering host-provided content). OverrideDEPLOY_HOST/DEPLOY_USERsecrets if your network/user differs. The private key secret must be namedSSH_DEPLOY_KEY.
Deploy keys (optional)
Helper scripts live in scripts/:
generate_deploy_key.shcreates an ed25519 keypair underpublic/keys/.add_deploy_key.shcan upload the public key to a Forgejo repo via API (requiresFORGEJO_TOKENand repo info).
Only public keys should be committed; private keys belong in runner secrets or on the host itself. See scripts/README_add_secrets.md for a detailed flow.