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
I did a quick test to evaluate this project. I spun it up with a docker compose file. I set the environment variables to disable http to https redirect. But all I got was a splash screen saying "generating config" that then redirects to https.
I have a few issues with this:
Users should not see a splash screen. Instead, I should be able to skip this whole "generating config step" and bake the config into the docker deployment image. I am evaluating for a scale-to-zero scenario so this extra latency is a negative
@brandonkal i do not know if bunkerweb is even able to run this way maybe have a look at bunkerized Nginx witch is the previous product if your fine with not receving updates anymore or if you want a simpler setup since all the bunkerized products are kind of advanced with the active Core Rule Set maybe try https://nginxproxymanager.com/
Hi, as of now no all-in-one images are available but maybe in the near future.
TheophileDiot
changed the title
[BUG] Redirects to https despite config disabling this
[FEATURE] Have a all-in-one image with the scheduler and Buinker
Oct 21, 2024
TheophileDiot
changed the title
[FEATURE] Have a all-in-one image with the scheduler and Buinker
[FEATURE] Have a all-in-one image with the scheduler and BunkerWeb together
Oct 21, 2024
What happened?
I did a quick test to evaluate this project. I spun it up with a docker compose file. I set the environment variables to disable http to https redirect. But all I got was a splash screen saying "generating config" that then redirects to https.
I have a few issues with this:
How to reproduce?
Just run this docker compose
Configuration file(s) (yaml or .env)
Relevant log output
No response
BunkerWeb version
1.5.9
What integration are you using?
Docker
Linux distribution (if applicable)
No response
Removed private data
Code of Conduct
The text was updated successfully, but these errors were encountered: