peter/siftlode
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(repo): remove internal deployment plan, sanitize infra references

Browse source 
Drop docs/deployment-plan.md (internal planning doc, kept out of the repo) and
replace the personal lab DB IP and host names in the env/compose/deploy docs with
generic placeholders, so the repo is safe to make public later.
This commit is contained in:
npeter83 2026-06-14 23:20:02 +02:00
parent 0f9e14e56f
commit c19f4d9d31
5 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.forgejo/workflows/ci.yml
View file

@ -1,6 +1,6 @@
name: CI
# Lightweight validation on every push to main: type-check + build the frontend and
# byte-compile the backend. The image build and rollout happen on the the VPS host
# byte-compile the backend. The image build and rollout happen on the deploy host
# (see deploy/README.md); this just catches breakage early.
on:
push:

8
deploy/README.md
View file

@ -1,9 +1,9 @@
# Deploying Siftlode to the public VPS (the VPS)
# Deploying Siftlode to the public VPS
The public test instance runs on the the VPS VPS at **https://siftlode.b1fr0st.eu**, behind
The public test instance runs on a VPS at **https://siftlode.b1fr0st.eu**, behind
Caddy (which terminates TLS and reverse-proxies to the app on `127.0.0.1:8080`).
## Layout on the VPS
## Layout on the host
```
/srv/siftlode/
@ -17,7 +17,7 @@ the small VPS.
## First-time setup
1. DNS `A`/`AAAA` for `siftlode` → the VPS (done via the your DNS provider CLI).
1. DNS `A`/`AAAA` for `siftlode` → the VPS (via your DNS provider).
2. Caddy vhost block `siftlode.b1fr0st.eu { reverse_proxy 127.0.0.1:8080 }` (+ the shared
security-headers snippet), then reload Caddy.
3. `git clone` this repo to `/srv/siftlode/src`.

4
deploy/deploy.sh
View file

@ -1,7 +1,7 @@
#!/usr/bin/env bash
# Roll out the latest main branch to the public the VPS instance.
# Roll out the latest main branch to the public VPS instance.
#
# Layout on the VPS:
# Layout on the host:
# /srv/siftlode/src git clone of this repo (build context + compose file)
# /srv/siftlode/.env secrets, mode 0600 (never in git)
#

2
docker-compose.localdev.yml
View file

@ -1,4 +1,4 @@
# Local development against the central (Proxmox) Postgres.
# Local development against the central Postgres (an always-on host that also runs the scheduler).
#
# Runs only the webapp/API — no local database, no scheduler — pointed at the shared
# DB on the server. You see the same live data the 24/7 backfill is filling, and you

2
docker-compose.prod.yml
View file

@ -1,4 +1,4 @@
# Public VPS (the VPS) deployment — hardened, single-host, behind Caddy.
# Public VPS deployment — hardened, single-host, behind Caddy.
#
# Differs from docker-compose.server.yml (the home/LXC stack): the database is NEVER
# published, the app binds to 127.0.0.1 only (Caddy terminates TLS and reverse-proxies it),