Drupal CMS Tests One-Command Deployment With Railway and Fly.io

Railway and Fly.io Support Is Available Only in the 2.x Development Branch
A blue promotional graphic from The Drop Times titled "Getting a Drupal Site Online Should Be Easier". A workflow diagram shows Drupal CMS running locally with DDEV and terminal commands deploying the site to Railway or Fly.io. A note highlights experimental support in Drupal CMS 2.x with a planned release in version 2.3.0.

Developers testing the Drupal CMS 2.x development branch can deploy sites to Railway or Fly.io using new DDEV commands, according to Drupal CMS product lead Pamela Barone. In a 12 November 2026 post, Barone described the experimental deployment workflow, which is planned for Drupal CMS 2.3.0 but is not yet part of a stable release.

The initiative addresses what happens after a Drupal CMS site has been built locally. Barone said that small and experimental sites can struggle to find hosting that combines affordability with a practical deployment experience. She stressed that the team does not have hard data showing hosting is a barrier to Drupal adoption and is testing the idea rather than claiming it has solved the problem.

Deployment Commands Are Available in Development

After creating a site using the Drupal CMS 2.x development branch and the Drupal CMS Helper development dependency, developers can run ddev exec dr deploy:railway for Railway or ddev exec dr deploy:fly for Fly.io. The post provides setup commands using the Forma site template, although other templates can be selected. The deployment prompts the user to create an account or sign in. Both providers offer trial credits; Barone notes that Fly.io requires a credit card to deploy.

On the first run, the deployment script installs the selected provider's command-line tools, generates configuration, exports site content and configuration, and deploys the application using a custom Dockerfile. The process creates web and database services and performs a fresh installation from the export. On later runs, provided that a valid project reference remains, the script deploys the application and configuration rather than repeating the initial site-content export. The post does not establish that editorial content changes made on a running production site will be synchronised automatically.

A Hosting Experiment, Not a Cost Guarantee

Barone previously tested ten shared hosts and concluded that they were not a feasible recommended pathway for Drupal CMS sites. She contrasted inexpensive shared hosting with Drupal-oriented platform services that provide more capable development tools but may cost too much for very small sites. For her own infrequently updated single-author website, she instead exported Drupal to static HTML using Tome and hosted the result on Netlify; she noted that this does not address the needs of most multi-author Drupal sites.

The Drupal CMS roadmap labels the work Launch on command, and Barone said the team expects to include it in Drupal CMS 2.3.0 before the end of 2026. That remains a projected release target, not an announced stable availability date. The Drupal CMS project page lists 2.2.9, released on 11 November 2026, as the latest stable release at the time of this report.

Barone credited lead architect Adam Globus-Hoenich with the implementation. The team selected Railway and Fly.io as initial providers because they offered the required deployment tools, and it is asking the Drupal community for feedback in the #drupal-cms-development Slack channel before deciding how far to extend the approach.

The new commands could reduce some of the manual steps between local development and deployment, but the project's own account does not provide a cost comparison, uptime evidence or evidence of broad adoption. Developers evaluating the experimental workflow still need to assess hosting charges, ongoing operations, data persistence and deployment suitability for their sites.

Disclosure: This content is produced with the assistance of AI.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.

Related Drupal Initiatives

Upcoming Events

Latest Opportunities