Ubuntu 22.04 base image and s6 Overlay v3

[alexjustesen]

To-do/Issues

• the docker container is not picking up on environment variables passed through the run command which is causing DB migrations to fail. Fixed in Fix permissions issues with S6 Overlay 3.x #43

Changelog

Changed

• base image to serversideup/php:beta-8.1-fpm-nginx which uses Ubuntu 22.04 and supports multi-arch, closes Ubuntu 22.04 and multi-arch support #32
• service file structure to match s6 Overlay v3 suggestions

Build and run

docker build . -t speedtest-tracker

docker run -d --name speedtest-tracker \
    -p 8443:443 \
    -e "DB_CONNECTION=mysql" \
    -e "DB_HOST=mysql" \
    -e "DB_PORT=3306" \
    -e "DB_DATABASE=speedtest_tracker" \
    -e "DB_USERNAME=root" \
    -e "DB_PASSWORD=password" \
    -v /path/to/app/data:/app \
    speedtest-tracker-2204

[jaydrogers]

I might be able to submit a PR for your app.

Before I do, could you let me know your thoughts on a few questions?

Questions

1. How do you want the local development experience to be?

Do you want spin and everything to be based from Docker? See Financial Freedom for example Laravel repo with Spin →

2. How do you expect deployments to happen?

I assume you want a docker image in Docker Hub (or comparable)? I assume your target market of people are "home labbers" looking to monitor their home internet connection?

[alexjustesen]

@jaydrogers thanks for the offer!

1. I've got sail currently as the dev env but I'm open to using spin instead but def not my current priority.
2. Correct the target is "home labbers" and I'm trying to wrap everything into one container that has a build process to easily get started. Planning on publishing to ghcr and/or Docker Hub

[jaydrogers]

Ahhh okay, sorry I was a confused from earlier. Diving into this more, looks like you have this a lot further along that I initially expected. You can basically ignore my first post 😆

I am taking a look into your issue that you posted earlier (serversideup/docker-php#82). I am seeing if I can replicate it on my end.

I was confused by your COPY .env.docker .env line, but now I think I see your use case for this. Let me do some further testing and I will keep you posted. 👍