Deployment

Git Workflow

Trunk-based development with protected main branch:

Create feature branch
Push → GitHub Actions runs lint checks
PR requires 1 approval + CI pass
Squash merge to main
Manual git pull on server

CI Checks

Check	Tool	Scope
Python lint	ruff	`bot/`, `mcp-server/`
JavaScript lint	eslint	`consilium/server.js`
PHP syntax	php -l	`wordpress/mu-plugins/`

Server Deployment

Code reaches production via symlinks:

/opt/reincarnatiopedia/bot/scripts     → /opt/lighthouse-bot/scripts
/opt/reincarnatiopedia/consilium/      → /root/consilium/server.js
/opt/reincarnatiopedia/wordpress/      → WordPress mu-plugins directory
/opt/reincarnatiopedia/frontend/       → /var/www/consilium/

After git pull, services pick up changes immediately. Restart only needed for Node.js (Consilium) and Python (MCP server, bot) services.

Why No Auto-Deploy?

Intentional. With a single production server running 200 language subdomains, every deploy is reviewed manually. Safety over speed.

​Deployment

​Git Workflow

​CI Checks

​Server Deployment

​Why No Auto-Deploy?

Deployment

Git Workflow

CI Checks

Server Deployment

Why No Auto-Deploy?