Web security depends on following boring ole’ best practices, like keeping your software up-to-date. This makes it fairly dull, unlike Hollywood portrayals of IT security. However, if disaster strikes, you need a plan in place to fix things, fast.
Automate Your Database Backups Using GitHub Actions
Today we are releasing version 1.0 of our Platform.sh Database Backup and S3 Sync GitHub Action that will allow you to take a database dump from a site hosted on platform.sh and sync that database dump to an AWS S3 bucket that you specify. We are utilizing this action with a scheduled workflow on a number of sites to automate database backups without running on any of our own infrastructure. We hope you find this tool useful, and let us know if you encounter any issues!
One of Tugboat’s most compelling features is that it is fast, but that hasn’t stopped us from pursuing making it even faster. We wanted to turn our tugboat into a speedboat.
At the time of Yarn’s debut, it brought big advancements to npm’s performance and workflow along with the introduction of lock files. A lot of time has passed since then and with the arrival of a native npm lock file, I was under the impression that more recent npm development had rendered the benefits of Yarn obsolete.
Deploying the latest changes to your site can take many forms. Understanding the steps involved and why each one matters will help prevent deployment surprises.
Chromatic has used Travis CI for nearly five years for our continuous integration needs; building every pull request, checking our changes against code standards, running automated tests, etc. On March 12, 2019, we canceled our Travis subscription and began running our builds elsewhere. Why make a change now? It’s simple, really.
