-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to use custom templates in Lizmap-Docker? #25
Comments
Hi! And tell us if it works. If it is ok, could you please make a Pull Request? |
Thank you very much! |
I'm sorry. I reopen this topic because I find error in the work of the administration interface after changes. In log-files in /lizmap/www/var/log/errors.log I see In log-files in /lizmap/var/log/nginx/lizmap_access.log If I delete line about lizmap-themes-default in docker-compose.yml - all work correct. |
It appears that there is some content needed in the directory required for lizmap to run properly. (Lizmap is not fully docker friendly yet :-/). My guess is that you will have to modify the docker-compose file to fit your needs: i.e explicitely mount the files/dir required for your needs. |
Thank you. |
@skvo1977 Could you change your PR accordingly? Thanks. |
Hello there. I find why this issue is triggered. Adding the following line will erase some content in I instead added this line I may need to add a line for every modules I want to rewrite, but it's not a problem for me. If you have a better solution I'll take it :) |
With the image of Lizmap 3.6 and higher, there is no more static files into |
Hello!
I'm using Lizmap 3.5 with Docker on Ubuntu Server 20.04.
And I have a question
Сan i use custom templates as described in documentation here ? - https://docs.lizmap.com/current/en/publish/customization/template.html
And where should the template files be placed in this case?
Do I need to add a folder "var/themes/default" in section "volumes" for "lizmap"- servieces in docker-compose file?
Thanks you.
The text was updated successfully, but these errors were encountered: