When running in Tomcat, ART is using WEB-INF/work to store its configuration and the uploaded templates files. This directory is deleted when the webapp is updated. ART could have a configuration (given by system property for example, default to $HOME/.art ) which tell where configuration files should be put
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello I also copy the content of WEB-INF to do an update. I think it is not practical, art-custom-settings.json must be saved and restored I guess. We need something external (like system property) to avoid save and restore process.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When running in Tomcat, ART is using WEB-INF/work to store its configuration and the uploaded templates files. This directory is deleted when the webapp is updated. ART could have a configuration (given by system property for example, default to $HOME/.art ) which tell where configuration files should be put
Hi, you can modify the WEB-INF\art-custom-settings.json file and set an "external" work-dir.
https://sourceforge.net/p/art/wiki/Manual/#custom-settings
When I do updates, i have a script where I copy only these files back into the tomcat-dir :art_custom_settings.json and groovy_whitelist.txt
Hello I also copy the content of WEB-INF to do an update. I think it is not practical, art-custom-settings.json must be saved and restored I guess. We need something external (like system property) to avoid save and restore process.