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
When trying to upgrade to 1.5.x I see that in the docs https://docs.bunkerweb.io/1.5.0/migrating/ BunkerWeb configuration is no more stored in a plain file (located at /etc/nginx/variables.env if you didn't know it).
So for the migration do the new version we plan to setup a postgressql
But the examples section does not reflect those needed change as there is not database configured.
In the examples it looks like the database in 1.5.x is not a requirement.
Proposed solution (optional)
Create an example with a database or drop the documentation requirement of a database.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Hi @vdveldet, thank you for opening this feature request. Indeed the database is sort of optional, as by default it will create a SQLite one at /var/lib/bunkerweb/db.sqlite3 and you don't have to provide one.
@fl0ppy-d1sk , indeed it is related to the DATABASE_URI as shown in the folders.
I have also seen this in the Kubernetes example here, but not in linux or docker-compose environment.
Since these environments are on 1 server, the need to have this setup is less, but I'm running bunkerweb as frontend loadbalancers in docker, there it could be usefull.....
Description
When trying to upgrade to 1.5.x I see that in the docs https://docs.bunkerweb.io/1.5.0/migrating/
BunkerWeb configuration is no more stored in a plain file (located at /etc/nginx/variables.env if you didn't know it).
So for the migration do the new version we plan to setup a postgressql
But the examples section does not reflect those needed change as there is not database configured.
In the examples it looks like the database in 1.5.x is not a requirement.
Proposed solution (optional)
Create an example with a database or drop the documentation requirement of a database.
Code of Conduct
The text was updated successfully, but these errors were encountered: