You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While there's a lot of configs possible with bunkerweb via environmental variables and the ui/db there's still configurations that aren't accessible even though they are supported in nginx.
Similar to how vanilla nginx and open-appsec-nginx work it'd be nice to have a clear and documented path to have bunkerweb nginx load template files on start.
This would make it so much easier for people to migrate their configs and use Bunkerweb. Like it takes no time at all to copy *.template files from nginx to open-appsec-nginx or any other nginx-based app and have everything configured the same and up and running using template files.
Implementations ideas (optional)
Implementation would ideally be similar to how vanilla NGINX currently works, any file in the /etc/nginx/templates/ directory is processed at start and added to the nginx config
What's needed and why?
While there's a lot of configs possible with bunkerweb via environmental variables and the ui/db there's still configurations that aren't accessible even though they are supported in nginx.
Similar to how vanilla nginx and open-appsec-nginx work it'd be nice to have a clear and documented path to have bunkerweb nginx load template files on start.
This would make it so much easier for people to migrate their configs and use Bunkerweb. Like it takes no time at all to copy *.template files from nginx to open-appsec-nginx or any other nginx-based app and have everything configured the same and up and running using template files.
Implementations ideas (optional)
Implementation would ideally be similar to how vanilla NGINX currently works, any file in the /etc/nginx/templates/ directory is processed at start and added to the nginx config
docker-config-nginx.yml example:
plex.conf.template example
Code of Conduct
The text was updated successfully, but these errors were encountered: