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.
Poor website architecture and performance planning has struck again, this time leaving 24,000 families in the state of Illinois disappointed and burdened by the crash of the Empower Illinois scholarship tax credit site.
dnscontrol is an open-source tool written in Go by the fine folks at Stack Exchange that allows us to configure our DNS records in a JS file that can be committed to version control and published on demand. With this configuration in git, we can now easily review changes through our normal pull request workflow, as well as getting a full log of any changes made over time.
Using Drush to sync databses (drush sql-sync) is a valuable tool, but it is not always an efficient choice when dealing with large databases (think over 1GB).
