Rails Server — Process Management

Manage named persistent Rails processes: the web server, background job workers, asset build watchers, and any other long-running services the project needs. The equivalent of Replit's workflow manager — bind a name to a command, start it, check its status, read its logs, restart it after changes.

When to Use

• User asks to "run the app", "start the server", "boot Rails"
• After making code changes that require a server restart
• After adding/changing environment variables
• User asks "is the server running?", "check the logs", "why isn't it starting?"
• Starting background job workers (Sidekiq, Solid Queue, Good Job)
• Setting up a full dev environment with multiple services

When NOT to Use

• One-off commands (running tests, a migration, a rake task) — use Bash directly
• Debugging application errors — fix the code first, then restart
• Production deployments — use the deploy skill instead