Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions launch/monorepo.html.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: Monorepo and multi-environment deployments

Check failure on line 2 in launch/monorepo.html.md

View workflow job for this annotation

GitHub Actions / Vale linter

[vale] reported by reviewdog 🐶 [Vale.Terms] Use 'monorepo' instead of 'Monorepo'. Raw Output: {"message": "[Vale.Terms] Use 'monorepo' instead of 'Monorepo'.", "location": {"path": "launch/monorepo.html.md", "range": {"start": {"line": 2, "column": 8}}}, "severity": "ERROR"}
layout: docs
nav: apps
redirect_from: /docs/reference/monorepo/
Expand Down Expand Up @@ -45,6 +45,32 @@
fly deploy --build-target worker
```

## Combining options

When you specify a working directory, the `--config` and `--dockerfile` paths are relative to the working directory (build context), not your current directory.

For example, given this structure:

```
repo/
├── flyio/
│ └── my-app.toml
└── my-app/
└── Dockerfile
```

This won't work, because `./flyio/my-app.toml` doesn't exist inside `./my-app`:

```cmd
fly deploy ./my-app --config ./flyio/my-app.toml
```

Instead, use a path relative to the working directory:

```cmd
fly deploy ./my-app --config ../flyio/my-app.toml
```

## Examples

**Use a different fly.toml file per environment**
Expand Down
Loading