81–90 of 507 posts
The most popular currently is probably https://www.netlify.com/ - 100% free. If AWS + CloudFront is too difficult and you don't mind spending a few bucks, it's pretty easy to get started with LightSail - about $3.50 a month.
Specifically Netlify Drop: https://app.netlify.com/drop You don't even need to create an account, just upload a zip of your files.
Earlier quoted context omitted.
An S3 bucket is intended as storage, not retrieval. Downloading from S3 means grabbing shards. You should put a proper CDN, like CloudFront or Cloudflare, in front.
> You should put a proper CDN, like CloudFront or Cloudflare, in front. I understand what you're saying, but why? I assume the site in question is pretty low volume. What's wrong with serving directly from S3?
Also you get a little bit of protection from someone sending lots of traffic to make you spend $$$
Earlier quoted context omitted.
Why, if his monthly bill is 83 cents, and he values his time? Does not using a CDN impact performance in a crippling way that neither me nor the poster you're replying to understands?
The big gain with putting Cloudfront in front of it is you can have HTTPS.
Check with your ISP, they often offer some 10 or sometimes 50! MB of free space to host your homepage and images under an account url, eg: http://example.com/~you . Uploading is easy, just FTP your files to their server and your done! I miss the old days :(
I host my personal site this way.
I also host about 100 mostly-static mostly-low-use websites at work similarly: with Apache on a couple of VMs. They are more reliable than the free versions of Netlify etc, and the systems work to maintain 100 static websites is little different to maintaining 5 static websites.
I use https://nearlyfreespeech.net for my static site. It isn't free -- it is pretty cheap -- but it has a lot going for it. It requires no custom tooling -- I upload via rsync. This makes it trivial to migrate to a new provider if necessary. I develop my site locally, then rsync it up. I have a custom domain pointed at the site, and also a custom .htaccess, so I have a good amount of control over the site. I do thin…
My site is entirely statically-served; I have one script for rebuilding my local copy and a second for rsyncing to my NFS host.
https://workers.cloudflare.com/
GitHub Pages or Netlify for sure. With either of these options, your static site can be set up to deploy whenever there's new commits to the specified branch. Me and a friend mentor for Code Louisville, and we're able to get the beginner frontend students up and running very quickly using these options - they're free and much easier to use.
I discovered Netlify through Netlify CMS. I had a pretty bad opinion about Netlify CMS, so I was pretty sure Netlify was going to be at least as bad. Damn, I have never been so wrong: - the interface is so intuitive I never opened the documentation - this is FAST (the bottleneck to see my website live is now my browser cache) - no need to create a Github Actions pipeline to deploy, just say "hey, my repo is here" - a…
GitHub Pages or Netlify for sure. With either of these options, your static site can be set up to deploy whenever there's new commits to the specified branch. Me and a friend mentor for Code Louisville, and we're able to get the beginner frontend students up and running very quickly using these options - they're free and much easier to use.
One of their neat features is the ability to spin up "pull request sites" automatically, so you can share versions of your site with stakeholders before it's made live.