Migrating from Render
View as MarkdownMove a Render web service to Atlasflow.
Render web services and Atlasflow projects work similarly: both deploy a container from a Git repository. The main changes are the fixed port and moving from render.yaml to project settings.
What maps over
| Render | Atlasflow |
|---|---|
| Web service from Git | Project from GitHub |
| Docker or native runtime | Dockerfile or automatic builds |
| Environment groups / vars | Environment variables |
| Custom domains | Custom domains |
Steps
- Create a project from your GitHub repository.
- Match the build. If you used a Dockerfile on Render, point Atlasflow at the same Dockerfile path. If you used a native runtime, rely on automatic builds or add a Dockerfile.
- Set the port to 3000. Render uses a dynamic
PORT; Atlasflow expects port 3000 bound to0.0.0.0. - Replace
render.yaml. Atlasflow doesn't read a config file; set the root directory, Dockerfile path, branch, and variables in project settings. - Health check on
/. Render lets you set a custom health check path; Atlasflow checksGET /. Make sure/returns a 2xx status. See Container requirements. - Recreate variables, deploy, test the preview URL, then move your domain.
Things to know
- Background workers and cron jobs map to separate projects running the relevant command as a long-lived process.
- Managed databases are coming soon; bring your own for now.
Next steps
- Configuration: replace
render.yamlwith project settings. - Container requirements: port and health check.
- Custom domains: move your domain.