-
The easiest way to switch from your current ssh -> git pull deployment to CI deployment is the switch to Deployer. https://deployer.org/ which is doing something similar but in a blue/green deployment way. A github action for it can look like this:
-
Cloudways
Cloudways' Black Friday Offer - 1st Choice of Developers. Cloudways: Devs' 1st choice for managed hosting! Pick from top-tier Cloud providers like DigitalOcean, AWS, and GCE. Limited-time deal: 40% OFF for 4 Months + 40 Free Migrations.
-
-
If you’re deploying in AWS and depending on your app I’d highly recommend using https://bref.sh/. When we changed it made our deploy pipeline so much simpler and our AWS bill much cheaper. Plus infrastructure as code is so useful (we don’t have dedicated dev ops in a team of about 20). Things like adding GD, upgrading PHP, or even adding a redis server become 1 (or a few) lines of change which you can PR and test on staging just like other code changes.
-
IMO you wouldn't want them posted as comments, the build status shows up as a pass/fail on the PR as well as each commit (see https://github.com/more-cores/discord-commands/pull/10 and the checkmark/x next to each commit hash). Clicking on it will provide more details on the build.
-
Same thing with git commits. Something like commitizen. It forces a specific format of your commits. And if you're using an associated issue/bug tracker that can automatically link to commits you can set up to format like that.
-
Don't build your own. Use something like Platform.sh for hosting/dev hosting, and Lando for local development. Then move on with life.
