Explore >> Select a destination
|
You are here 
|
raviramanujam.com | ||
| | | | |
benjamincongdon.me
|
|
| | | | | AWS is a great place to host static content: Bandwidth / hosting costs are very cheap if you're at "hobbyist" scale, you get great availability, and AWS gives you free SSL termination / certificate management for HTTPS if you get everything setup correctly. | |
| | | | |
sanderknape.com
|
|
| | | | | ||
| | | | |
fourteenislands.io
|
|
| | | | | I was web browsing through the different taxi companies operating in Stockholm this morning when I eventually ended up on taxi020.se which responded with an HTTP 404 error. As I read the code and message for that error my search for waiting time at the airport terms and conditions got all of a sudden more interesting. Taxi 020 merged with Sverigetaxi in 2016 and is now part of the Cabonline Group. | |
| | | | |
willhaley.com
|
|
| | | My guide is largely based on the Deploying to Amazon S3 guide from Semaphore, but with some pre-requisite steps and fine-tuning to S3. Switching your DNS provider for your domain to Amazon's Route 53 may be a requirement. Depending on your DNS provider, your DNS configuration, and your willingness to jump through hoops like setting up a reverse proxy on another server, you may be forced to transfer your domain. You should absolutely read the DNS and hosting section of Amazon's Static Website Using a Custom Domain guide before proceeding. | ||
