UI on port 80

[ThatDeltaGuy]

What would you like Grimmory to do?

Either set the UI port to 80, or have a similar setting as other servers allowing the user to change the port:

For the opds server keep 6060 if static, or add in the same options if not. With the 'URL Base' defaulting to /api/v1/opds (or /opds if /api/v1 is needed, and append to the end) and a check to make sure that, if the ports are the same for both, the opds server has a URL base set.

What problem does this solve for you?

I'm running grimmory in unraid on its own IP address. However, because the container UI port is 6060 i still have to append 6060. it's not a big issue on its own, I can use a reverse proxy for most things, but when accessing it locally I have to remember the port. Again, not a big issue on its own, but I’m running 30+ different containers, quite a few of which are also on different ports.

There are also some instances( certain devices, server monitoring etc.) where a port number cannot be used.

Anything else?

Slightly related to: https://github.com/orgs/grimmory-tools/discussions/1476. Moving to port 80 would also open up the possibility of supporting 443 for https in the future

Want to help out?

Just sharing the idea for now

Before submitting

• I've searched existing discussions and this hasn't been suggested yet
• I've reviewed this report and have completed it as fully as I can

[imnotjames]

You can use the environment variable BOOKLORE_PORT and set it to 80

[ThatDeltaGuy]

That works to get me on port 80, I do think it should be a configurable option within the UI though.

[obviouslyallie]

The UI would need a container restart anyway. I'm unsure if that's helpful or just redundant.

[obviouslyallie]

I think I'm going to close this one as an alternative method already exists. This is the intended purpose of the environmental file. Additionally having a UI option could possibly be confusing: do we want people to set it again? Leave it blank?