Skip to content

Railway Marketplace release

The source repository is public at github.com/Schero94/clouddev-ai-sovereign-workspace. No Railway template ID or deploy URL exists until Railway creates and publishes a reviewed draft. Check the current release status before each publication step. A successful local build or IaC plan is not proof of a live deployment. The product is not one-click verified.

The Railway documentation was checked on 2026-10-25. The current documented flow is to create a template from a tested Railway project or start in the Template Composer, then publish it from the template page. The railway templates create CLI command creates an unpublished draft from a project. It does not publish a Marketplace template by itself.

Release gates before creating the template

  1. Keep the public source repository free of .env, SSH private keys, Railway tokens, and provider credentials. The current GitHub history was scanned with Gitleaks before the source push and returned no findings.
  2. Run the unit, security, Compose, image-build, mock-provider, SSH, Git, and session recovery checks. Record the actual output in GATES.md.
  3. Close image-security gates G15 and G17. Keep the router dashboard and inference endpoints private.
  4. Sign in to the intended personal Railway workspace and create a fresh test project in that workspace. Do not use an existing personal or company project for the release test.
  5. Run railway config plan in that project and inspect every addition, change, and deletion. Railway's agent skill requires a separate explicit approval of the exact plan before railway config apply; do not apply a plan by assumption.
  6. After an approved plan is applied, verify the live region, domains, TCP proxy endpoints, private networking, volume mounts, and Serverless/App Sleeping setting. Run the Desktop to mobile to Desktop flow and restart recovery against that Railway deployment.
  7. Restore the workspace, Forgejo, PostgreSQL, and OmniRoute data from a real backup in an isolated test. A backup procedure is not a tested restore.

Configure the Template Composer

  1. Use the clean test project and choose Create Template. Starting from a new template in Workspace Settings is also documented. Confirm the final draft contains only clouddev-ide, clouddev-git, clouddev-postgres, and clouddev-router.
  2. Verify the GitHub source and Dockerfile settings that IaC declares for all three app services. The workspace uses repository root . with Dockerfile services/ide/Dockerfile. Forgejo uses root services/forgejo with Dockerfile Dockerfile. The router overlay uses repository root . with Dockerfile services/omniroute/Dockerfile, which pulls the pinned upstream image.
  3. Set every service and volume to europe-west4-drams3a. Keep the workspace, Forgejo, and router data volumes at their declared mount paths. Leave each stateful service at one replica.
  4. Generate an HTTPS domain for clouddev-ide on port 8080 and for clouddev-git on port 3000. Add a TCP proxy for port 2222 on each of those services. Do not create a public domain or proxy for PostgreSQL or OmniRoute.
  5. Add every generated secret from RAILWAY_TEMPLATE_VARIABLES.md using its ${{secret(64, "0123456789abcdef")}} value. preserve() in IaC keeps an existing Railway value. It does not generate a secret for a fresh template deployment. Keep the ten secret entries and their descriptions in .railway/template-variables.json synchronized with all preserve() calls.
  6. Require SSH_AUTHORIZED_KEYS as a user-specific value containing one or more operator Ed25519 public keys. This cannot be filled with a maintainer key. Never ask for the matching private key.
  7. Leave provider credentials out of the template. The deploying owner must connect their own provider in the authenticated OmniRoute dashboard, then create a scoped inference key through onboarding.
  8. Check registration, health paths, restart policy, volume mounts, public access, and Serverless/App Sleeping in the draft. The always-on workspace must have sleeping disabled. Do not infer this from a local IaC type-check.
  9. Create the template draft only after the configuration is complete. Then deploy that draft into a second fresh project and run the release checks.

Publish the tested template

  1. From Railway's Template page, choose Publish on the reviewed draft and complete the Marketplace form. Include the overview, deployment instructions, support contact, source license, and images. Choose AI/ML if it is still offered in the Composer. The prepared overview text is in RAILWAY_TEMPLATE_OVERVIEW.md.
  2. Keep the template private until the security, cross-device, restore, and fresh-project deployment gates pass. The publication form does not replace those tests.
  3. Railway controls whether it marks a template as verified. Do not claim a badge unless Railway has granted it on the published template page.
  4. After publication, copy the exact template URL Railway provides into the Deploy on Railway section in README.md. Do not invent a template code or URL.

The current CLI also supports publishing template metadata after Railway has created a draft and returned its real code. Do not run this example until the personal target workspace and deployment gates are confirmed:

npx --yes @railway/cli@5.71.0 templates publish <TEMPLATE_CODE> \
  --category AI/ML \
  --description "Deploy and Host CloudDev AI on Railway" \
  --readme-file docs/operations/RAILWAY_TEMPLATE_OVERVIEW.md \
  --json

The Template Composer remains available for the same publication workflow.

Post-publication checks

  • Deploy the published template into another fresh project.
  • Check that generated secrets differ from the test deployment and the SSH public key belongs to the deploying operator.
  • Test workspace browser auth and key-only Remote-SSH from clean clients.
  • Test a private Forgejo push/fetch and an authenticated OmniRoute mock or approved provider request.
  • Verify shared files and resumable session history across desktop and mobile.
  • Restart the workspace and verify files, CLI settings, and supported manual session recovery.
  • Restore all four persistent data sets from backup in an isolated project.

Official Railway references