Migrating to Bahriya
Move an existing application from another platform to Bahriya, step by step.
6 articles
Migrate from Docker Compose to Bahriya
Migrate from Docker Compose to Bahriya: map each compose service to its own container, replace service-name networking with secrets, and deploy per region.
4 minMigrate from Fly.io to Bahriya
Migrate from Fly.io to Bahriya: translate your fly.toml into container settings, recreate your secrets, map regions directly, then cut your domain over.
3 minMigrate from Heroku to Bahriya
Migrate from Heroku to Bahriya: turn your Procfile and buildpack into a Dockerfile, split Config Vars into env vars and secrets, and cut over your DNS.
4 minMigrate from Railway to Bahriya
Migrate from Railway to Bahriya: containerise each service, split variables into env vars and secrets, wire databases in via connection secrets, and deploy.
3 minMigrate from Render to Bahriya
Migrate from Render to Bahriya: map web services, workers and cron jobs to containers, move render.yaml config into env vars and secrets, then cut over DNS.
3 minMigrating to Bahriya
Migrate to Bahriya from any platform: containerise your app, move config into env vars and secrets, deploy to your regions, then cut your domain over.
4 min