cumsek/nix
cumsek/nix
Watch
2
0
Fork
You've already forked nix
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

revert(sites): take the wysi containers off cum-sites for now #18

Merged
marti merged 1 commit from feature/remove-wysi-deployment into main 2026-10-02 19:37:39 +02:00
Conversation 0 Commits 1 Files changed 9 +7 -585
marti commented 2026-10-02 19:37:13 +02:00
Owner

Takes the wysi deployment off cum-sites for now, and sends wysi727.com back to cum-sites:4727 the way it worked before 42c2ee0.

Changes

  • Removes hosts/cum-sites/modules/wysi{,-client,-server}.nix and DEPLOY-wysi.md. The cum-sites modules list is empty again.
  • nginx: wysi727.com proxies to 192.168.1.204:4727, and api.wysi727.com is gone.
  • cum.nix: wysi.port = 4727. wysi-sigma-back goes back to 1323, since it only moved to 1423 to make room for the wysi API.
  • cum-sites firewall: opens 4727 and 1323 again and closes 3100.
  • Postgres: removes wysi from the database list. The existing database, role and .secrets.yaml values are left in place.

The changes from those commits that aren't about wysi stay: the nginx forwarded-header fix, Postgres backups, nixos/nfs.nix and update.sh.

Verification

  • cum-sites and cum-services both evaluate (nix eval .#nixosConfigurations.<host>.config.system.build.toplevel.drvPath).
  • nginx vhosts evaluate to wysi727.com -> :4727, sigma.wysi727.com -> :4000 and sigma-api.wysi727.com -> :1323.
  • Not deployed yet. After merge, run ./update.sh cum-sites and then ./update.sh cum-services.

🤖 Generated with Claude Code

Takes the wysi deployment off cum-sites for now, and sends `wysi727.com` back to `cum-sites:4727` the way it worked before 42c2ee0. ## Changes - Removes `hosts/cum-sites/modules/wysi{,-client,-server}.nix` and `DEPLOY-wysi.md`. The cum-sites modules list is empty again. - nginx: `wysi727.com` proxies to `192.168.1.204:4727`, and `api.wysi727.com` is gone. - `cum.nix`: `wysi.port = 4727`. `wysi-sigma-back` goes back to 1323, since it only moved to 1423 to make room for the wysi API. - cum-sites firewall: opens 4727 and 1323 again and closes 3100. - Postgres: removes `wysi` from the database list. The existing database, role and `.secrets.yaml` values are left in place. The changes from those commits that aren't about wysi stay: the nginx forwarded-header fix, Postgres backups, `nixos/nfs.nix` and `update.sh`. ## Verification - `cum-sites` and `cum-services` both evaluate (`nix eval .#nixosConfigurations.<host>.config.system.build.toplevel.drvPath`). - nginx vhosts evaluate to `wysi727.com -> :4727`, `sigma.wysi727.com -> :4000` and `sigma-api.wysi727.com -> :1323`. - Not deployed yet. After merge, run `./update.sh cum-sites` and then `./update.sh cum-services`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) 
wysi727.com goes back to proxying cum-sites:4727, as it did before the
container deployment. The wysi-client/wysi-server modules, the runbook and
the api.wysi727.com vhost are gone, and wysi leaves the Postgres database
list (the database, role and secrets are left in place, so re-adding it is
one line).

sigma-api returns to port 1323: it only moved to 1423 to make room for the
wysi API. The cum-sites firewall opens 4727 and 1323 again and drops 3100.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
marti merged commit bd8ff15e88 into main 2026-10-02 19:37:39 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cumsek/nix!18
No description provided.