Skip to content

Commit

Permalink
Merge pull request #116 from igor-alexandrov/mention-app-port-upgrade
Browse files Browse the repository at this point in the history
Mentioned changing app_port setting during upgrade
  • Loading branch information
dhh authored Sep 29, 2024
2 parents 3545c45 + feeca85 commit 6772b9a
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions docs/upgrading/configuration-changes.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,13 @@ The `traefik` configuration is no longer valid. Instead you can configure kamal-

If you were using custom Traefik labels or args, see the proxy configuration whether you can convert them.

Be aware that by default kamal-proxy forwards traffic to the container port 80, this is because we assume your container is running Thruster, and it listens on the port 80. If you are running a different service or port, you can configure the app_port setting:

```yaml
proxy:
app_port: 3000
```

kamal-proxy supports common requirements such as buffering, max request/response sizes, and forwarding headers, but it is not the full breadth of everything Traefik can do.

If you don't see something you need, you can raise an issue and we'll look into it, but we don't promise to support everything — you might need to run Traefik or another proxy elsewhere in your stack to achieve what you want.
Expand Down

0 comments on commit 6772b9a

Please sign in to comment.