The site with guess which URL?
Find a file
datagreier2 d070ab8083
All checks were successful
Forgejo Runner CI / Build (self-hosted Forgejo runner) (push) Successful in 45s
card color even darker
2025-12-10 12:04:43 +01:00
.github/workflows rsync set up to delete subdir. Excluded. 2025-12-10 10:23:04 +01:00
public Changed color to not communicate Russian imperialism 2025-12-10 11:46:37 +01:00
scripts runnes settings updated 2025-12-10 05:07:36 +01:00
src card color even darker 2025-12-10 12:04:43 +01:00
.gitignore add deploy_key.pub to public/keys and protect private keys in gitignore 2025-12-10 04:52:57 +01:00
eslint.config.js first commit 2025-12-10 04:29:23 +01:00
index.html card logic, truncation 2025-12-10 10:50:47 +01:00
package-lock.json consolidate: enable Fast Refresh, remove RefreshRuntime shim, tidy up 2025-12-10 06:38:12 +01:00
package.json consolidate: enable Fast Refresh, remove RefreshRuntime shim, tidy up 2025-12-10 06:38:12 +01:00
README.md rsync set up to delete subdir. Excluded. 2025-12-10 10:23:04 +01:00
vite.config.js consolidate: enable Fast Refresh, remove RefreshRuntime shim, tidy up 2025-12-10 06:38:12 +01:00

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/ to DEPLOY_DIR (default /srv/www/socialist.live) on the runner. Requires the runner to have write access (or sudo).
  • Remote deploy (default): uses SSH_DEPLOY_KEY and syncs dist/ over SSH to ${DEPLOY_USER:-aron}@${DEPLOY_HOST:-172.17.0.1}:${DEPLOY_DIR} (rsync excludes data/ to avoid clobbering host-provided content). Override DEPLOY_HOST/DEPLOY_USER secrets if your network/user differs. The private key secret must be named SSH_DEPLOY_KEY.

Deploy keys (optional)

Helper scripts live in scripts/:

  • generate_deploy_key.sh creates an ed25519 keypair under public/keys/.
  • add_deploy_key.sh can upload the public key to a Forgejo repo via API (requires FORGEJO_TOKEN and 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.