I recently moved my web hosting to AWS. (Blog post here.) I knew from friends that hosting a static site on AWS is relatively cheap and easy, so I was sure I’d be able to make the switch. However, I didn’t take the time to consider that not all the elements of my site were static.
While the instructions for redirecting a www subdomain to the apex (base) domain on an AWS-hosted site may not encompass many steps, I had to employ a fair amount of googling and testing in order to get this working on my site. My website is nikym.org, and I wanted to ensure that any requests to www.nikym.org redirected to nikym.org. Furthermore, I wanted any requests to an HTTP version of the site to redirect to the HTTPS version.
I recently decided to move my personal website hosting to AWS. I did this for a few reasons:
Our team recently updated Learn.co from React 15 to 16, and I took part in a subsequent sprint to update our React Router from version 2 to version 4. React Router 4 is conceptually very different from the previous versions; the creators wrote the new version entirely in React with an API that followed common React patterns. The Route is now just a component which makes nesting routes an easier task. This design difference meant we had to implement React Router 4 in a completely different manner than we used 2. Here are some of the biggest changes we made in our upgrade.
In my time so far on the dev team, CSS has been my most-improved skill. As a student I avoided it whenever possible. I like debugging and finding the exact line of code that does something I don’t expect. CSS bugs have always felt harder to isolate that way. I can swap values in and out while examining elements in the console, but if something goes wrong, I don’t get an error message guiding me to the source. By far the hardest CSS situations I’ve had to troubleshoot involve stacking context.