Port set in env file #2861

New Issue

OVERLORD · 2026-02-05T05:29:28+03:00

OVERLORD commented

2026-02-05 05:29:28 +03:00

Originally created by @Stoiker on GitHub (Jun 21, 2022).

Describe the feature you'd like

The port the application listens to can be set in the env-file.

Describe the benefits this would bring to existing BookStack users

To use Bockstack behind a reverse proxy (like nginx) it would be great if the application could be configured in such a way that the port it listens to is set in the env-file.

My current problem is that with podman port 80 is restricted as mapped port in a pod and I want nginx to use that port.

Would that be feasible?

Can the goal of this request already be achieved via other means?

Not afaik

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundemental request

How long have you been using BookStack?

0 to 6 months

Additional context

No response

Originally created by @Stoiker on GitHub (Jun 21, 2022). ### Describe the feature you'd like The port the application listens to can be set in the env-file. ### Describe the benefits this would bring to existing BookStack users To use Bockstack behind a reverse proxy (like nginx) it would be great if the application could be configured in such a way that the port it listens to is set in the env-file. My current problem is that with podman port 80 is restricted as mapped port in a pod and I want nginx to use that port. Would that be feasible? ### Can the goal of this request already be achieved via other means? Not afaik ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundemental request ### How long have you been using BookStack? 0 to 6 months ### Additional context _No response_

OVERLORD added the 🔨 Feature Request label 2026-02-05 05:29:28 +03:00

OVERLORD closed this issue

2026-02-05 05:29:31 +03:00

OVERLORD commented

2026-02-05 05:29:32 +03:00

@ssddanbrown commented on GitHub (Jun 21, 2022):

Hi @Stoiker,
None of the release content within this core project/repo listens to a port.
The port is usually handled by the webserver in use.

If you're using one of the community containers, usually they expose 80 by default but you can usually map a different host port to port 80 of the container, when running/starting the container.

@ssddanbrown commented on GitHub (Jun 21, 2022): Hi @Stoiker, None of the release content within this core project/repo listens to a port. The port is usually handled by the webserver in use. If you're using one of the community containers, usually they expose 80 by default but you can usually map a different host port to port 80 of the container, when running/starting the container.

OVERLORD commented

2026-02-05 05:29:41 +03:00

@Stoiker commented on GitHub (Jun 21, 2022):

Hi @ssddanbrown
that makes sense. Doing multiple container recently, lead to a mix-up in my mind ...
Sorry for the inconvenience.

@Stoiker commented on GitHub (Jun 21, 2022): Hi @ssddanbrown that makes sense. Doing multiple container recently, lead to a mix-up in my mind ... Sorry for the inconvenience.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#2861