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

New Issue

AtHeartEngineer · 2025-07-08T08:41:35-04:00

AtHeartEngineer commented

2025-07-08 08:41:35 -04:00

Originally created by @michaelbeaumont on 5/15/2025

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 5/15/2025* ### 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 🤷

AtHeartEngineer closed this issue

2025-07-08 08:41:35 -04:00

AtHeartEngineer added the feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature feature labels 2025-07-08 08:41:36 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pocket-id#174