Config generator not updated and creating errors #2303
MrCybertux
started this conversation in
Technical
Replies: 2 comments 1 reply
-
Hi @MrCybertux, Thanks for opening this issue—we appreciate you bringing it to our attention! We're already aware of this problem but haven't had the chance to update compatibility with version 1.6 yet. We'll address this as soon as possible 🚀. Sorry for any inconvenience caused, and thanks again for your patience! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Converting this into a discussion as this isn't a bug with BunkerWeb. We'll keep you updated |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What happened?
The config gen was not updated and is in my experience quite buggy.
Even if set to 1.6.1 it still gives out wrong compose configs:
also importing a config is not possible if i change at least 1 setting in the config (in this case just activate default CRS):
How to reproduce?
Use the online config tool and change 1 setting before importing. (Import problem)
Set version to 1.6.1 in config editor and get the compose file. (Not Updated config)
Configuration file(s) (yaml or .env)
Relevant log output
BunkerWeb version
1.6.1
What integration are you using?
Docker
Linux distribution (if applicable)
No response
Removed private data
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions