@Sinnbeck, do you also have a testing server setup or just the main server? Also, do you use Docker with Sail or mainly without and what role does it play in your flow?
As far as I could figure out, Docker is mainly used on the development side and especially to get you started or basically to remove all that pain of setting up the dev env. But for some ppl who use Laravel and PHP stack on daily basis it doesn't add much value, does it?
@tudosm Deployment processes look different from project to project; there’s no one size fits all. But there is some commonality between them.
What you’re describing is commonly referred to as CI (continuous integration) and CD (continuous deployment). So yes, in a lot of projects I’ll use GitHub Actions to run tests when I commit. You can then also set up restrictions so that only commits with passing tests are merged to your main branch. If you then automatically deploy code when merged into your main branch (and you’ve ensured only code with passing tests is merged to your main branch), then you’re also ensuring that only code where tests have passed ends up getting deploying into production.
Docker is a way of containerising apps. You can use them in development, you can use them in production, but you don’t have to. Deploying could be FTP-ing or SSH-ing files to a server, or triggering a deploying using a service like Forge, or deploying to an cloud provider like AWS or an IaaS like Heroku. It completely depends where and how you host your website, as to how you’d do around deploying it.