![]() On all our previous hosting platforms, we lacked the flexibility to scale up quickly when we needed to, be it to accommodate more websites or higher user volumes for a particular site. Future-proof and scalable for growing websites With Pantheon, they renew automatically, so it’s quick, reliable and disruption-free. Despite our best-laid plans, this manual approach was always subject to human error, so we couldn’t guarantee to clients that it would go without a hitch. Previously, we had to use a manual process to remember to order or renew certificates, then upload them, to ensure they didn’t expire. Pantheon also automates HTTPS (SSL) renewals using Let’s Encrypt, which saves us loads of time and ensures our clients' users are always protected. Within an hour or two, we can have 25 websites updated and ready to test, whereas previously it could have taken us at least that long per website. The custom upstreams and automation allows us to throw code around easily, update all our sites in one place, and do it using a single command. When we need to make across-the board updates to our websites, such as a Drupal 8 security update, Pantheon makes it super efficient for our development team. We can see exactly what copies we have on the platform, hold them securely for as long as they’re needed, and delete them without a trace once we’re finished. Pantheon ensures that the whole process is quick, dynamic and low risk. Then once the code change is complete, there’s a seamless browser-based process to implement it on the live site. With Multidev, we can have multiple copies of the same site, with different people working on them, if needed. That’s vital when a university relies on their site to drive student applications or a health charity needs to provide advice on contraception and STIs, 24 hours a day, seven days a week. With Pantheon, however, Multidev allows our team to make a separate copy of the live site in just a couple of minutes, which our devs are safe to play with and break without affecting our clients or their users. ![]() Well, whenever we needed to fix a bug or investigate a data problem on a client’s website, we used to have three options:ĭo it in a staging environment that may not be fully up to dateĬreate a whole new staging environment for the changes to take placeĮach of these options was less than ideal for us and our clients, either because of the inherent risk involved or the time, it would take us to prepare stuff before we could even get started. So why did we move? And what difference does it make where we run our client sites? At IE Digital, we recently migrated the vast majority of our Drupal and WordPress websites onto Pantheon-much to the delight of our development and support teams.
0 Comments
Leave a Reply. |