Volume path overlap with existing paths inside image #162

The /htdocs webroot inside the container is currently recommended to be configured as volume. However since it contains files required for the application to function, it causes issues with very common use-cases which override the volume content at mount, leaving an empty directory.

The following use-cases are currently impossible without workarounds (see below):

• Bind volumes with Docker/Podman/Compose
• Kubernetes volumes

A workaround is to copy the original content of the image in the volume with an init container, prior to the main container starting. But this rather hacky and not ideal.

The following changes would be required at minimum:

• Allow defining the location of the SQLite database file: that way it can be configured to be read from its own dedicated (sub-)directory and configured as volume
  • I see a non-empty database is already present on the image's FS. If it is somehow seeded and built into the app that's also bad practice and instead it should be created from scratch at container start
• Only mount /htdocs/storage/app/public as a volume to persist file uploads: AFAIK the rest of the webroot doesn't need to be persisted