Persistent Themes and Plugins Instructions Not Working

[queenkjuul]

I have followed the instructions for setting up persistent Plugins and Themes directories, but the instructions are not working. I suspect I see the issue, but I am not certain, and have not yet had time to do any testing/try to propose a fix. I initially thought the issue was because I had translated the provided command to a Docker Compose file, but I have the same problems when using the raw Docker CLI. It is not a permissions problem: the container is able to write to the shared volumes (and bl-content is populated after install)

Looking at PR #13 , I'm seeing that the change from mv to cp has been reverted in current main branch. I suspect this might be the origin of the issue? Though the actual docker logs suggest there may be more going on:

bl-themes directory is empty, initializing...
cp: can't stat '/tmp/bludit/bl-themes/*': No such file or directory
chown: unknown user nginx.
bl-plugins directory is empty, initializing...
cp: can't stat '/tmp/bludit/bl-plugins/*': No such file or directory
chown: unknown user nginx.

When I get into the container to poke around, I see that the rest of nginx/html is owned by user www-data, not nginx. It's also apparent that /tmp is completely empty when the entrypoint script runs.

So, the fixes I will attempt if I have time would be:

• go back to cp -r instead of mv on line 27 of Dockerfile
• Swap chown nginx. for chown www-data. in docker-entrypoint.sh

and if the issue is that /tmp is getting wiped between when the container is created and when the entrypoint is run (I don't think this is the case, but I need to re-read some Docker documentation to know for sure) then I would suggest using /opt/bludit to store an untouched stock version of the Bludit distribution, which the entrypoint script can copy to the other directories as needed.

[queenkjuul]

changes in PR #21 work for me at least