Closed lykaios closed 12 months ago
There may be a problem during docker initialisation (lizmap installation don't perform completely, speciallay the db installation).
Within the folder where you copy the lizmap-docker-compose files, there must be a folder "lizmap" , can you try and remove it , or simply do a configure.sh clean
in order to force un clean install ?
hi @nworr thanks for your feedback.
Let me give that a whirl and get back to you.
Its relevant to note, we are using an existing postgres container (we are trying to integration into a stack we have, rather than create a separate one). However, I did include the "init" script which creates the "lizmap" database and that definitely works correctly.
Ok, so I took a peek into configure.sh
and it looks like all clean does is delete .../var
and a few other install directories.
I suspect its something to do with the config in there - can you explain which one of the ini files controls the db setup?
Also, more generally, the container-stack design doesn't quite align with industry standards for Docker/Distributed systems... Are you guys concentrating any resources there or is it pure open source contributions?
Also, more generally, the container-stack design doesn't quite align with industry standards for Docker/Distributed systems... Are you guys concentrating any resources there or is it pure open source contributions?
Can you elaborate a few things quickly? Maybe @dmarteau will have some ideas.
If you think it's needed, feel free to provide a PR. Step by step
This issue is missing some feedbacks. 👻 Please have a look to the discussion, thanks. 🦎
You can go ahead and close this as I don't have time to do an infrastructure fundamentals; cheers!
This issue is missing some feedbacks. 👻 Please have a look to the discussion, thanks. 🦎
What is the bug?
I am attempting to setup lizmap 3.6 within the docker-compose stack provided here: https://github.com/3liz/lizmap-docker-compose
Although I am able to connect to the Postgres database (so I know credentials are good), there seems to be an issue creating the admin user.