Uh oh!
There was an error while loading. Please reload this page.
initial env var ingestion for rev proxy configs - #586
Conversation
LinuxServer-CI
commented
Sep 4, 2025
I am a bot, here is the pushed image/manifest for this PR:
|
LinuxServer-CI
commented
Sep 4, 2025
I am a bot, here is the pushed image/manifest for this PR:
|
thelamer
commented
Sep 4, 2025
Made the env tamplates directory a dedicated thing so it will not delete anyone's custom configs. |
LinuxServer-CI
commented
Sep 14, 2025
I am a bot, here is the pushed image/manifest for this PR:
|
LinuxServer-CI
commented
Oct 11, 2025
I am a bot, here is the pushed image/manifest for this PR:
|
LinuxServer-CI
commented
Nov 11, 2025
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I have tested this pretty thoroughly at this point, it is bolt on logic so will not have an effect on any existing setups unless you can think of any possible reason someone would be passing an env var starting with "PROXY_CONFIG_" to a swag container.
The most basic string is incredibly useful to do subdomain setup to a port using a service name as :
This basically just works in most cases subdomain to a port, but all the options are there to get way more complex like in the case of Plex:
The docced examples show the - array member syntax with escaped $ being double $$ and the whole thing being wrapped in single quotes but the object syntax like the plex example above is much more forgiving.
I think this is a good first step and maybe down the line we can look at using jinja templates for the ini generation and get everything in an env var format if possible.