search

mhzawadi / docker-picocms

GNU Lesser General Public License v3.0
1 stars 0 forks source link

Why so many volumes? #7

Open aptonline opened 2 years ago

aptonline commented 2 years ago

Not an issue more an observation, why are there so many volumes that need mapping? would it not make more sense to just map /html directory to a single volume/directory?

Generally interested not trolling 👍🏼 .

mhzawadi commented 2 years ago

Hello,

I wanted to give you the ability to keep all the user data across container destroys, other wise you all your content and configs would get lost

aptonline commented 2 years ago

I get why you map a local directory to the container to preserve user data across upgrades but I was enquiring why you have so many volumes.

Couldn't you simply map the local directory to /var/www/html/ and have the container populate the separate directories within it (themes, config,content,assets,plugins)?

mhzawadi commented 2 years ago

The answer to this is:

When I build the image, PicoCMS is unpacked into /var/www/html. If you have a volume for just all of /var/www/html you would get all of PicoCMS, it also cuts down on the amount of messing about the startup script has to do.

Also you may not want some of the user data persistent