ConceptsServices
An upload
ferry up sends a folder from your machine to the server. Ferry builds it and deploys it.
ferry up packs the folder as a .tar.gz archive.
1 / 3
A service with no repository and no image deploys an upload.
Upload a folder
ferry up my-app # packs ., creates my-app if needed, uploads and deploys
ferry up my-app --dir ./app # another directoryWhat goes into the archive
| Files | In the archive |
|---|---|
Files that .gitignore, .ignore or .ferryignore exclude | No |
.git, node_modules, target, .venv, venv, __pycache__, Python virtualenvs | Never |
Hidden files such as .env.example or .npmrc | Yes |
| Symlinks that point outside the directory | No, with a warning |
ferry up follows .gitignore also outside a git repository. .ferryignore wins over the other ignore files. Thus a !pattern line in .ferryignore adds a file that git ignores.
ferry deploy my-app, or Manual deploy in the dashboard, builds the newest upload again.
ferry up also works on a service that has a repository or an image. That deploy builds your local files and tells you so.
The archive can be 512 MiB at most. For the limits on the server, see Limits.