bug/docs: Permission & folder sturcture issues when installing with mounted volumes

[Blboun3]

Issue filing pre-requisites

• I've checked the documentation.
• I've looked for similar issues both Open and Closed.
• Ive tried clearing both cache and cookies in my browser or tried opening the app in the Incognito/InPrivate window.

Describe the bug

When installing with mounted volumes instead of named volumes I've encountered many errors.

1. The folders on the drive HAVE to be owned by user 82:82 (related to **** Configure SQLite3 database **** Operation not permitted #54, feature request: support PUID + PGID environment settings #56, as that would help with this as well)
2. The proper folder structure and required files have not been created in the mounted folders even when permissions were correct, this led to many errors including the software not being able to find the SQLite databse, the .env file or the Laravel migration/setup files

Steps to Reproduce the issue

Permission issues

1. Download the official docker-compose.sqlite.yaml file
2. Replace named volumes with local folders, i.e. /var/lib/invoiceshelf/{data,modules} owned by your user, root, or any other user for that matter. Even if I made sure it has 777 permissions it didn't work.

Files & folders issues

1. As changing folder ownership to 82:82 seems to solve the previous issue it's not over, as it seems like the files and folders do not get created in mounted rather than named volumes, thus files like the SQLite database or .env file HAVE to be created manually for the software to be able to find and edit them.

Expected behavior

The software installing normally like with named volumes

Actual behavior

The software fails due to permission and file ownership issues and if that gets solved it is unable to install due to it missing critical files.

InvoiceShelf version

v2.3.3

Database type

SQLite

Server OS

Linux (Debian 13)

My solution that worked

1. Make sure the base folder is owned by 82:82 (invoiceshelf/)
2. Start the container with named volumes but also mount your base folder (invoiceshelf/)
3. Go through the whole install and make sure invoiceshelf is working
4. docker exec bash inside the container and manually copy the files from their in-container locations to folder in your mounted volumes (i.e. /var/www/html/Modules to /mnt/invoiceshelf/modules)
5. Remove the named volumes and mount your proper foolders inside mounted volumes
6. Voilá it works.

[didotb]

can confirm this is an issue.
Workaround I've done for now which worked was:

1. to use bind mount ./storage:/var/www/html/temp/storage and ./modules:/var/www/html/temp/modules.
2. pull up /bin/sh for the container to determine the user and group id number of user www-data (it was 82 for me).
3. copy all files from /var/www/html/ storage and modules, and paste them into the temp folder's storage and modules.
4. chown the temp folder's storage and modules on the host side based on the id number of user www-data.
5. re-mount the bind to the non-temp folders.

Before doing this I tried doing a chown to the folders for user www-data, but I found out the id number was different for the host and the container so that didn't work.
This should work for the rest of the bind mounts.