Getting startedDashboard tour
Create a service
The New service button opens one form. You fill it from the top to the bottom.
Service type. Choose what the service is, for example a web service.
1 / 6
Do it
On the Services page, click + New service. Fill the sections. Then click Create and deploy.
The sections
| Section | What you set |
|---|---|
| Service type | Web service, private service, background worker, cron job or static site. See Services. |
| General | The name. |
| Source | Git repository, Docker image or Upload later. |
| Build & deploy | The runtime (auto-detect or one that you choose), the build command, the start command, the port and the instances. |
| Custom domains | More hostnames for the service. |
| Environment | Variables. Add them one by one, import a .env file, or insert a reference to a datastore. |
| Env groups | The groups to link. |
- Connected account lists the repositories of a connected GitHub or GitLab account. Search the list and choose one.
- Add account authorizes one more account on the page of the provider. Then you come back to the form. The form keeps what you entered.
- Repository URL accepts each git URL.
- With the two choices, Branch is a list that Ferry reads from the repository. The two choices have the auto-deploy switch.
Ferry creates the service with no source. Then you send the code with ferry up: an upload.
A cron job has no start command. It has a command and a schedule. A static site has a publish directory.
Advanced adds these settings:
- The root directory and the Dockerfile path, for a monorepo.
- The health check path.
- A persistent disk.
- The memory limit and the CPU limit of each instance. See Resource limits.