Wouldn’t you like to know when MailGun fails to deliver an email? Or worse still, when someone complains about an email you sent?
MailGun can notify you about the following events:
Clicked Complained Delivered Failed Opened Unsubscribed There’s just one catch: You have to write your own webhook, then subscribe to those events with your webhook’s URL. If that thought left you cross-eyed, fear not! The reign of cloud computing has made this simpler than it used to be, especially the introduction of functions as a service.
Grab a bowl of buttery popcorn because the saga continues! The end of the previous chapter saw our intrepid little Rails app camping happily on Heroku. This latest chapter in the hosting chronicles brings with it a twist: not just a change in host, but a complete migration from one programming language to another.
Onward for the Why’s, How’s, and Gottchas of the switch.
Static site generators aren’t new, but something about the fresh simplicity of Hugo is turning heads. We’re in the early stages of the Gartner Hype Cycle , but expect to see media outlets abuzz with tales of Hugo “making waves” and “disrupting stuff”. Even de facto strongholds like WordPress have begun losing ground to the inexorable spread of the Static Invasion.
But between all the skirmishes, turf wars, and soap-box-soliloquies, how do you know if Hugo is the right match for your site, or if it’s even worth the hype? Here’s what you need to know, reader’s digest style. (from Migrating WordPress to Hugo, Step-by-Step )
The year was 2016. I was a hobbyist with ideas to burn. Naturally, I needed an inexpensive hosting provider for my latest web app. Where would I start? Who would prove to be the elusive “hostess with the mostest?”
This is the story of my migration to and from DigitalOcean, AWS, and Heroku – the trial and error, the pros and the pain points. You’ve seen the archetypal hero’s tale. Now cinch up your belt, oil your sword.