/explore
|
You are here 
|
info.varnish-software.com | ||
| | | | |
blog.bigdinosaur.org
|
|
| | | | | ||
| | | | |
blog.ymirapp.com
|
|
| | | | | We all know how important it is to have a fast WordPress site. If your site is slow, people leave or don't make a purchase. It's also a signal Google uses to do... | |
| | | | |
truemped.github.io
|
|
| | | | | My usual web application stack for the past years was based on a nginx as reverse proxy in front of a number of Python processes. Static resources were served by nginx. Each Python process was stateless, state was stored in some kind of database. If the processes needed some shared ephemeral state like counters a local redis instance solved that. A battle tested common ground for Python based web applications. | |
| | | | |
philiplaine.com
|
|
| | | There are a bunch of blog posts and tutorials out there showing how to setup a static website on AWS. They all offer the same general solution with maybe some caveat. Route53 for DNS, CloudFront as a CDN to speed up content delivery, S3 to store the content, and ACM as a certificate provider. A good place to start off at when embarking on a new project is AWS own reference documentation. AWS static website project is a great example of this, and it will probably do a better job conveying the required information that I ever will. The only thing I think the example lacks is setting up it certificates for CloudFront. That was the source of most of my problems when setting up my static website, the very one you are on right now. There are many Stack Overflow qu... | ||
