281–290 of 507 posts
Have used the cache-everything trick for client sites back in the day to serve a top 15 post on /r/all from a $5 Wordpress box.
Man, I'm so glad to be out of that space...
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…
They recently published this blog post: https://blog.nearlyfreespeech.net/2021/01/19/free-speech-in-...
After reading this, I made the decision to move my hosting elsewhere. I have never hosted content that is even remotely political, and have no intention to do so. I had chosen to patron nearlyfreespeech based upon the belief that their conception of 'freedom of speech' matched my own. I believe 'freedom of speech' is not just a convenient vehicle for expressing my own political ideas, it is an important political idea in and of itself. I believe that the freedom for individuals to express their ideas without censorship is integral to a free and intelligent society. This post of theirs demonstrates that I had clearly misunderstood their beliefs.
It's clear that 'freedom of speech' is a controversial notion in today's society. If they market their service based upon their respect for so-called freedom of speech (it's in their name), I don't know what kind of crowd they expect to come. I came not out of a need, but based upon my political views. I imagine I'm a minority. I'm not interested in a host that markets itself in such a way, and then demonstrates that what they _really_ meant was that they want an environment where you're free to agree with their views.
Earlier quoted context omitted.
I use both pages.dev and netlify.com: pages.dev, even in open beta, is a fantastic product if it suits all your needs, but the limitations [0], if you hit them, are a dead-end and there are no ETAs as to when some of those limitations would be addressed. That is not the case with netlify.com which boasts a myriad of features, is equally as fast, production-ready, and competitively priced. With pages.dev, I believe, y…
There is a strong chance that when Pages comes out of beta, Worker Sites is going to be transitioned into Pages, at least thats kind of how I feel about some of the verbiage on this page: https://developers.cloudflare.com/pages/migrations/migrating...
we don't have any plans to get rid of workers sites! but we do think that for most people deploying static sites, pages is a better fit than workers sites.
when we do talk about the future of pages versus workers sites, we're generally talking about making it easier to deploy serverless functions /with/ your pages sites - providing better tooling and DX around that is a super high priority for us.
the interplay between workers serverless functions and static asset serving via workers sites is still a really strong use case (and IMO a thing that workers is uniquely capable of doing) that we don't have any plans to shelf. again, i wrote the docs here so this is on me if it came across as "we're getting rid of workers sites" - i'll take a shot at improving these docs and helping clarify that next week!
Earlier quoted context omitted.
Who would you consider good DNS hosts? I'm looking at setting up a static site and am new to the whole process
Gandi.net is my favorite - their motto is "No BS" and I've found that to be true.
Earlier quoted context omitted.
And also, who cares it's a static host and you can change to another one in an afternoon. There's zero lock-in when you're only rsyncing some files around. Just make sure you have total control over your DNS (buy a domain, put it on a good DNS host) and you really can't screw things up too badly.
Who would you consider good DNS hosts? I'm looking at setting up a static site and am new to the whole process
It's good security because APIs are just another way to gain access to your stuff, and an attacker controlling your DNS has _incredible_ access to ruin your life (steal email, impersonate you... the works).
It's bad though because increasingly we're automating certificates and other stuff through means of using DNS as proof (i.e. set a magic TXT record and lets encrypt will grant you a wildcard SSL cert for free) and many scripts need a DNS provider with good API.
So long way of saying for basic stuff where it's just you going into a dashboard and clicking around to change settings--Namecheap is great. Their DNS comes free with purchase of a domain for a couple bucks, you really can't beat that price.
If you need programmatic API access step up to someone who is running DNS as a core part of their business IMHO--Amazon Route 53, Cloudflare, etc. The bigger the better as they'll have more security resources, support good security practices like 2FA, hardware auth devices, etc. and just generally have more care taken with access to DNS. You'll pay more but you'll get more in the long run.
However, there are some limitations such as if you need to add custom headers.
If you need more customization, then S3/Cloudfront also works well too. I also use Netlify and had minimal issues.
I've tried Github pages, Netlify, and Cloudflare Pages. Moved last night to the latter. Github pages is fine, but the extra gh-pages branch is kind of annoying. It's fairly clear (for obvious reasons) that they mainly think about Jekyll users, though I had a Hugo blog there for a while. Netlify sounds great, but in practice I ran into an annoying issue that I couldn't resolve where I had to rerun every automatic buil…
I use both pages.dev and netlify.com: pages.dev, even in open beta, is a fantastic product if it suits all your needs, but the limitations [0], if you hit them, are a dead-end and there are no ETAs as to when some of those limitations would be addressed. That is not the case with netlify.com which boasts a myriad of features, is equally as fast, production-ready, and competitively priced. With pages.dev, I believe, y…
nope, we do unlimited sites on pages! here's the free plan [1]:
> 1 build at a time
> 500 builds per month
> Unlimited sites
> Unlimited requests
> Unlimited bandwidth
you can upgrade to the pro ($20/mo) or business ($200/mo) plans for more concurrent builds and builds per month. still not priced per domain or site!
I use https://sdf.org , but then my needs are very modest...
Love to see projects like this still in existence. I sometimes wonder if I would get some users who could also share a box and keep it going for 30 years.