Speed up Docker build and fix entrypoint permissions

[PseudoResonance]

The Docker entrypoint script runs artisan commands as root, which creates directories under storage/framework/cache/data that are owned by root. This causes errors when running the panel, as it's unable to write to parts of the cache. By running the commands as www-data instead, the permissions are kept unaffected.

I added the Dockerfile to the compose file, so that the image can easily be built from source if desired.

As the yarn install command can take a long time, I changed the Dockerfile to copy just the necessary package/yarn files for the installation first. Once that is completed, it copies the rest and builds the app. This sped up cached builds on my computer by about 80 seconds.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[PseudoResonance]

I have read the CLA Document and I hereby sign the CLA

[RMartinOscar]

We should run the entrypoint it self as www-data instead of forcing www-data on each commands.
I believe this change would be in supervisord
Or we can use su www-data on top of the entryscript (not sure about that tho)

Also now that we are using vite yarn needs to access vendor

panel/tailwind.config.js

Line 1 in a7a7c5b

import preset from './vendor/filament/support/tailwind.config.preset'

[PseudoResonance]

I didn't think running the whole entrypoint script as www-data would be good as entrypoint itself runs chown at the end, seemingly as a final attempt at making sure everything is good.

[PseudoResonance]

Also now that we are using vite yarn needs to access vendor

panel/tailwind.config.js

Line 1 in a7a7c5b

import preset from './vendor/filament/support/tailwind.config.preset'

It shouldn't need it to install the dependencies though, right? I don't know much about Vite.

[RMartinOscar]

Also now that we are using vite yarn needs to access vendor

panel/tailwind.config.js

Line 1 in a7a7c5b

import preset from './vendor/filament/support/tailwind.config.preset'

It shouldn't need it to install the dependencies though, right? I don't know much about Vite.

It does require it to build and its been changed to yarn build too

[PseudoResonance]

It does require it to build and its been changed to yarn build too

Ah, I see now. I think I got it working properly with this.

[lancepioch]

I've left you some feedback, thanks

[lancepioch]

Isn't this assumed by default, does this change anything?

[PseudoResonance]

No, I just tested, and docker compose build or docker compose run --build will only build images with a build section specified. Although I realized build: ./ can serve the same purpose as this, if the Dockerfile has the default name.

[lancepioch]

Confused why this is necessary when we do the copy below?

[lancepioch]

This definitely confuses me even more. Definitely don't want to reference this file anywhere in Docker.

[PseudoResonance]

These 3 files are the bare minimum required to run composer install. The reason app/helpers.php is required as well, is because it's specified as an autoload file in composer.json, so composer install --optimize-autoloader looks for it.

[PseudoResonance]

Also the reason behind splitting the install and build up like this is just optimizing for build caching. By only copying the dependency lists first, those first layers only need to rerun when the dependencies change. Then the entire codebase is copied as late as possible to minimize needlessly rerunning. GitHub actions can also be configured to utilize caching (although I didn't do that in this PR), which, with these changes, should help speed up the builds a bit.

Although this doesn't have as big of an impact anymore because of the Vite frontend rewrite. The majority of the build time is now taken up by yarn run build, but regardless, I tried to move it down as far as possible.