Skip to main content

​
Deployment

​
Git Workflow

Trunk-based development with protected main branch:
  1. Create feature branch
  2. Push → GitHub Actions runs lint checks
  3. PR requires 1 approval + CI pass
  4. Squash merge to main
  5. Manual git pull on server

​
CI Checks

CheckToolScope
Python lintruffbot/, mcp-server/
JavaScript linteslintconsilium/server.js
PHP syntaxphp -lwordpress/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.