So that your files and tools can grow together, fully under your ownership, through the ages.
The app can be easily tweaked for your own needs via an LLM - code is optimized for that.
P.S. And Golang seems to be great fit for this kind of software.
docker + php-fpm + php7 + larvel + nginx + redis + cron + worker + certbot
Server after the rewrite to Golang:
server, a 15MB no-dependencies binary that has everything.
Also if you don't need certbot anymore is your service managing its own ssl certs with letsencrypt? Isn't it generally easier to configure with a reverse proxy like nginx or caddy and terminate SSL at the edge? That's literally caddy's whole thing that it does SSL for you so that it doesn't concern your application.
Like, I should be able to open it even after a few years, and do some fixes or add some features.
Go's ecosystem seems to share this mindset.