🚀 Feature: Alternative to PORT variable for configuring frontend listening port #219

New Issue

OVERLORD · 2025-10-07T00:06:16+03:00

OVERLORD commented

2025-10-07 00:06:16 +03:00

Originally created by @michaelbeaumont on GitHub.

Feature description

Add FRONTEND_PORT instead of PORT for configuring the frontend's listening port.

Pitch

I'm trying to deploy pocket-id on Digital Ocean's app platform. Each docker container that runs gets to choose one "public HTTP port." In the case of pocket-id this should be the same as CADDY_PORT. Unfortunately, when choosing this port, Digital Ocean overrides the PORT variable. I don't know why. But the consequence of this is that only the frontend is ever reachable. Trying to set CADDY_PORT to be the same as the "public HTTP port" means changing PORT, which means an address/port conflict between the frontend and Caddy.

This is really bad UX from Digital Ocean so I would understand not working around it but at the moment this makes the upstream docker image unusable with DO's app platform

EDIT: apparently overriding PORT is a common workflow for PaaS 🤷

Originally created by @michaelbeaumont on GitHub. ### Feature description Add FRONTEND_PORT instead of PORT for configuring the frontend's listening port. ### Pitch I'm trying to deploy `pocket-id` on Digital Ocean's app platform. Each docker container that runs gets to choose one "public HTTP port." In the case of `pocket-id` this should be the same as `CADDY_PORT`. Unfortunately, when choosing this port, [Digital Ocean overrides the PORT variable](https://docs.digitalocean.com/support/how-to-troubleshoot-apps-in-app-platform/#http-port-configuration). I don't know why. But the consequence of this is that only the frontend is ever reachable. Trying to set `CADDY_PORT` to be the same as the "public HTTP port" means changing `PORT`, which means an address/port conflict between the frontend and Caddy. This is really bad UX from Digital Ocean so I would understand not working around it but at the moment this makes the upstream docker image unusable with DO's app platform EDIT: apparently overriding PORT is a common workflow for PaaS 🤷

OVERLORD added the feature label 2025-10-07 00:06:16 +03:00

OVERLORD closed this issue

2025-10-07 00:06:17 +03:00

OVERLORD commented

2025-10-07 00:06:20 +03:00

@kmendell commented on GitHub:

This is something we are already working on for another refactor and is apart of https://github.com/pocket-id/pocket-id/pull/520

CADDY_PORT is going away and only PORT will exist.

@kmendell commented on GitHub: This is something we are already working on for another refactor and is apart of https://github.com/pocket-id/pocket-id/pull/520 CADDY_PORT is going away and only PORT will exist.

OVERLORD commented

2025-10-07 00:06:20 +03:00

@michaelbeaumont commented on GitHub:

Closing this cause I've tested the image built from the above PR and it works! Thanks @kmendell

@michaelbeaumont commented on GitHub: Closing this cause I've tested the image built from the above PR and it works! Thanks @kmendell

OVERLORD referenced this issue

2025-10-07 00:09:06 +03:00

🚀 Feature: Support SameSite cookie attribute #286

Sign in to join this conversation.