Deploy from a repository
What Railyard reads from your repo and how it fills in the app for you.
Paste a Git URL (or pick a repo from GitHub). Before the first deploy Railyard reads the repository and fills in:
| It reads | It sets |
|---|---|
Gemfile, package.json, requirements.txt/pyproject.toml/manage.py, composer.json, mix.exs, go.mod, Cargo.toml, pom.xml | the framework, start command, port and release command (migrations) |
Procfile, Procfile.dev, app.json, render.yaml, railyard.yml | web and worker processes the repo declares |
dependencies (pg, mysql2, sidekiq, ecto_ch, redix, celery…) | the databases to provision and the job runners offered as workers |
.env.example, compose files, README.md, docs/*env*.md, config/runtime.exs | the variables the app documents — database host/user/password, public hostname, bind address and port are wired to what Railyard provisions; app secrets are generated |
| the repo’s default branch | the branch to deploy |
Nothing here is specific to one app: the same rules apply to every repository. Anything you set yourself always wins.
After the first deploy
Detection runs again on every deploy, so new job runners or documented variables show up without re-creating the app.