easypanel-deploy

EasyPanel Deployment Workflow

Guide the user through deploying to their EasyPanel instance using the ep_* MCP tools.

Process

1. Check existing projects: Use ep_list_projects (with includeServices=true) to see what's already deployed. This prevents creating duplicate projects.

2. Determine service type: Ask the user or infer from the codebase:

   • Static site or Node/Python/Go/Rust app -> App service (ep_create_app)
   • WordPress site -> WordPress service (ep_create_wordpress)
   • Development environment -> Box service (ep_create_box)
   • docker-compose.yml present -> Compose service (ep_manage_compose)

3. Create or select project:

   • If the target project exists, use it
   • If new, create with ep_create_project (name must be lowercase, alphanumeric, dashes, underscores)

4. Configure source: Based on how the code should get to EasyPanel:

   • GitHub repo: Use sourceGithub with repo URL and branch
   • Docker image: Use sourceImage with image name and tag
   • Dockerfile: Use sourceDockerfile with path to Dockerfile
   • Git repo: Use sourceGit with repo URL

5. Set up domains: Configure domain routing with ep_configure_app using the deploy setting. Default to HTTPS.

6. Set environment variables: If the project needs env vars, use ep_configure_app with env setting or ep_update_project_env for project-level vars.

7. Deploy: Trigger with ep_deploy_app (use forceRebuild=true if redeploying).

8. Verify:

   • Check service status with ep_inspect_app
   • Check system resources with ep_system_stats if needed
   • Suggest enabling GitHub auto-deploy with ep_github_deploy for repo-based projects

Key Rules

• Always check if the project/service already exists before creating
• Default to HTTPS for domains
• Ask about environment variables before deploying
• Suggest setting up GitHub auto-deploy for repo-based projects
• Use ep_service_stats to verify the service is running after deployment
• For WordPress, use ep_create_wordpress with initialize=true for a ready-to-use site