If the docker-compose.yml is used and the setup is recreated with docker-compose down and docker-compose up it is necessary to rerun the setup again. During setup partkeepr appears to generate some files stored in the web directory. Since they are currently not stored in any docker volume they are lost on recreation. I think that should be different.
For myself I just mounted an additional volume:
volumes:
partkeepr-data:/var/www/html/data
partkeepr-web:/var/www/html/web
There are several more files (in the app directory) touched during the setup process, which are reset on recreation. But it seems thats fine
Slightly different topic. Could you remove the #Not used for now hints in the docker-compose files. They appear to be working. I spend some time wondering why my manually loaded parameters.php oktopart key was overriden all the time :see_no_evil:
If the docker-compose.yml is used and the setup is recreated with
docker-compose downanddocker-compose upit is necessary to rerun the setup again. During setup partkeepr appears to generate some files stored in thewebdirectory. Since they are currently not stored in any docker volume they are lost on recreation. I think that should be different.For myself I just mounted an additional volume: volumes:
There are several more files (in the
appdirectory) touched during the setup process, which are reset on recreation. But it seems thats fineSlightly different topic. Could you remove the
#Not used for nowhints in the docker-compose files. They appear to be working. I spend some time wondering why my manually loaded parameters.php oktopart key was overriden all the time :see_no_evil: