engineering/make_post_sell
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases 2 Packages Wiki Activity Actions

docs: clarify prod rules — restarts ok, some servers ci-only not salt

Browse source
This commit is contained in:
russell@unturf.com 2026-04-06 13:45:29 -04:00
parent 08509629b6
commit c6d03bd9ae
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
CLAUDE.md
View file

@ -18,9 +18,9 @@
**ABSOLUTE RULE**: ALL fixes go through CI/CD and Salt. No exceptions.
- **NEVER** SSH into prod and run `ALTER TABLE`, `sqlite3`, or any direct DB command
- **NEVER** manually restart services, copy files, or apply patches via SSH
- **NEVER** bypass the migration system — if `alembic upgrade head` fails, fix the migration and push
- **The fix is always in the code.** Push to master → CI tests → Salt highstate → Alembic runs on every instance
- **The fix is always in the code.** Push to master → CI tests → deploy (Salt highstate or CI-direct) → Alembic runs on every instance
- Restarting services via SSH is fine for recovery, but the underlying fix must still go through code + deploy
**Why this matters**: MPS runs open source on multiple servers (makepostsell.com, memopoly.com, and any operator instance). A manual fix on one server leaves every other instance broken. The migration system exists to apply changes everywhere consistently.