I’m getting married!
Aside from being excited, I’m taking this as an opportunity to DIY some of the pieces of weddings that could involve code.
In this case, I set up a minimal build system with Webpack 4, cssnext, and babel. I haven’t had time to sit down and configure webpack from scratch for some time, so a couple loaders were new to me. I was pleasently surprised by webpack-merge for splitting development and production build configuration. I combined extract-loader and html-loader to manage css and html, but I’m not completely satisfied with this part of webpack.
I’m continuing to use nginx to host my websites and
recently upgraded to
https using Let’s Encrypt. I
took an additional step with this site and made the upgrade to
wasn’t quite the learning experience I expected…
I still managed to have some fun setting up my domain names.
While the primary url is
https://ourlittlewedding.love, I also
purchased two additional vanity hostnames:
cameronandaisha.love. To do it right, I wanted
each domain to work, across both http and https, with or without
minimal redirects. To do this, I created a shared ssl certificate for all six
Then it was a fairly simple matter of redirecting http traffic to the primary domain to ssl
and redirecting any traffic to a non primary domain directly to the primary one
There might be a more efficent way to structure the configuration, but this works well for me.