111–120 of 507 posts
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.
Pfffffft. It’s probably a personal site with 10 visitors a week. Let’s step back a little here.
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.
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?
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 :(
OVH offers 10MB hosting when you get a domain with them. With FTP access.
If it's a commercial project I don't see the point of paying a premium for the nice UX, hosting static files is easy enough and I don't have investors' money to waste. I would spend my money on a CDN like BunnyCDN and throw a file server behind it.
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 :(
The in-between days (after dial-up ISPs, but before "cloud" meant people forgot they could do things themselves) was to host the website on your own computer. For example, an old laptop, a Raspberry Pi, or an always-on-anyway desktop. 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 ver…
Earlier quoted context omitted.
The in-between days (after dial-up ISPs, but before "cloud" meant people forgot they could do things themselves) was to host the website on your own computer. For example, an old laptop, a Raspberry Pi, or an always-on-anyway desktop. 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 ver…
I'm not sure how you do this unless you have a static IP somehow? In my experience ISPs don't offer that to residential clients
Many routers have support for this and if your router runs dhcpcd you can tell it to issue the call when it renews the DHCP lease from your ISP, or simply cron job it.
If you're looking for ease of deployment I think something like org-publish. But that would require some setup - anything would really.