openvibers/breakroomsimulator Commits
Document production deployment on simulator.rest
Changes
@@@ -107,9 +107,18 @@ the rug — no external assets. Data persists to `data/*.json`.## Website & public hosting (simulator.rest)--The server now serves a marketing landing page at `/` and the game itself at `/play`.++The server serves a marketing landing page at `/` and the game itself at `/play`.Real screenshots for the landing page live in `public/img/`.++**Production** ([simulator.rest](https://simulator.rest)) runs the bare-metal setup below:++Cloudflare (proxied DNS) → nginx (Let's Encrypt TLS, websocket proxy, Cloudflare++real-IP restore) → the Node server as the `breakroom` systemd service in++`/opt/BreakRoomSimulator`. Deploying an update there:++++```bash++ssh <server> 'cd /opt/BreakRoomSimulator && sudo git pull && sudo npm install --omit=dev && sudo systemctl restart breakroom'++```++### One-command deploy (Docker + Caddy, automatic HTTPS)On any Linux server (1 vCPU / 1 GB is plenty to start):
@@ -107,9 +107,18 @@ the rug — no external assets. Data persists to `data/*.json`.
@@ -107,9 +107,18 @@ the rug — no external assets. Data persists to `data/*.json`.
## Website & public hosting (simulator.rest)
## Website & public hosting (simulator.rest)
-The server now serves a marketing landing page at `/` and the game itself at `/play`.
+The server serves a marketing landing page at `/` and the game itself at `/play`.
Real screenshots for the landing page live in `public/img/`.
Real screenshots for the landing page live in `public/img/`.
+**Production** ([simulator.rest](https://simulator.rest)) runs the bare-metal setup below:
+Cloudflare (proxied DNS) → nginx (Let's Encrypt TLS, websocket proxy, Cloudflare
+real-IP restore) → the Node server as the `breakroom` systemd service in
+`/opt/BreakRoomSimulator`. Deploying an update there:
+
+```bash
+ssh <server> 'cd /opt/BreakRoomSimulator && sudo git pull && sudo npm install --omit=dev && sudo systemctl restart breakroom'
+```
+
### One-command deploy (Docker + Caddy, automatic HTTPS)
### One-command deploy (Docker + Caddy, automatic HTTPS)
On any Linux server (1 vCPU / 1 GB is plenty to start):
On any Linux server (1 vCPU / 1 GB is plenty to start):