DevOps with Codex

Take your app from code to staging with Codex.

Keep working in your application repository. Give Codex Wodby context and operations through MCP, then move from a read-only assessment to an explicitly approved staging deployment.

Connect Codex Follow the walkthrough

A practical walkthrough

Work toward a result you can verify.

A reviewed migration plan and a staging deployment you can verify before scheduling production cutover.

  1. Step 1

    Check the connection in your repository

    After connecting Wodby, open Codex in the application directory. Use /mcp to check the server, then ask Codex to identify the Wodby projects it can access.

    Confirm the organization and project before asking for a deployment. Stop here if authentication or access is incomplete.

    Codex step 1 prompt
    Use get_wodby_guidance to load wodby2-get-started. Check my Wodby connection and list the projects I can access. Do not create or change anything.

  2. Step 2

    Map the existing app to a Wodby stack

    Have Codex inspect dependency files, build scripts, environment variable names, workers, and persistent data needs. Review the service mapping and migration gaps before creating anything.

    Keep the existing codebase. Check database compatibility, uploads, scheduled jobs, and external dependencies. Do not paste secret values into the conversation.

    Codex step 2 prompt
    Use Wodby’s wodby2-migrate guidance to inspect this repository and plan its migration to Wodby. Identify required services, configuration changes, data transfer, likely downtime, and blockers. Do not create resources, connect to my current hosting, or change anything.

  3. Step 3

    Deploy and verify an isolated staging copy

    Once you accept the plan and grant the required permissions, ask Codex to prepare staging. Follow deployment tasks, then verify runtime status and the application itself.

    Test a real application request, data access, uploads, and any background workers. Keep email, webhooks, and production jobs isolated. Production data transfer and DNS changes require a separate decision.

    Codex step 3 prompt
    Use the approved migration plan to prepare a staging copy on Wodby. Confirm the target and costs before creating resources. Keep production hosting, data, and DNS unchanged. Isolate workers, scheduled jobs, email, and webhooks. Ask before copying data.

A successful task is only the first check.

Keep the deployment task reference, application checks, unresolved issues, and rollback limits with the migration plan. Ask for a cutover checklist only after staging meets your acceptance criteria.

These prompts guide the agent; they do not replace access controls. Choose scoped Wodby permissions and authorize changes deliberately.

Set up CodexReview access boundaries →All agent workflows →