3 ms·

I’m a forty year old idiot that still just uses a web server running on a VPS. If I want publicly accesible preview I'll scp them to a temp folder on the web se

I’m a forty year old idiot that still just uses a web server running on a VPS. If I want publicly accesible preview I'll scp them to a temp folder on the web server. I am probably missing out on something by not using Netlify but I still haven't been able to figure out what. (Caveat, I’m the sole developer on all my projects; maybe that affects the calculus somehow)

deleted 5y ago
[deleted]
sneak 5y ago
Most SSGs expect the site to be deployed to the root of a domain, not in a subdirectory. Unless all of your URLs are relative (including fonts, css, anything in js, et c) your approach probably won't work. Also, your sole VPS will fall over nearly instantly with any significant amount of traffic; the web is a lot bigger in terms of eyeballs these days than it was when we started out. These static services aren't bound by the capacity of a single machine.
- velcrovan 5y ago
  > Also, your sole VPS will fall over nearly instantly with any significant amount of traffic Wow, haha...no. Especially not with a static site. Even for a wordpress site, a $5 VPS can easily handle in the tens of millions of hits per day, and if that's not enough just add a CDN in front.
  - sneak 5y ago
    If they’re evenly distributed throughout the day, you have a gigabit port, and aren’t cpu throttled because shared hardware. A $5 VPS can handle less than a thousand or two connections per second, generally, and will fall over (even serving a static site) if linked simultaneously from a big subreddit and the HN front page during PST business hours. Using Netlify or a service like it saves you having to administer and keep running an httpd, and “just add[s] a cdn in front”. It’s also free, and not $5.
is_true 5y ago
I do the same. Need to handle traffic? Cloudflare.
canyonero 5y ago
Netlify shines in a git based workflow with teams (deploy previews on every pull request, collaborative tools, etc). For a solo dev, I can understand the limited appeal if you already have a workflow that works for you.

deleted 5y ago

[deleted]

sneak 5y ago

Most SSGs expect the site to be deployed to the root of a domain, not in a subdirectory. Unless all of your URLs are relative (including fonts, css, anything in js, et c) your approach probably won't work. Also, your sole VPS will fall over nearly instantly with any significant amount of traffic; the web is a lot bigger in terms of eyeballs these days than it was when we started out. These static services aren't bound by the capacity of a single machine.

velcrovan 5y ago
> Also, your sole VPS will fall over nearly instantly with any significant amount of traffic Wow, haha...no. Especially not with a static site. Even for a wordpress site, a $5 VPS can easily handle in the tens of millions of hits per day, and if that's not enough just add a CDN in front.
- sneak 5y ago
  If they’re evenly distributed throughout the day, you have a gigabit port, and aren’t cpu throttled because shared hardware. A $5 VPS can handle less than a thousand or two connections per second, generally, and will fall over (even serving a static site) if linked simultaneously from a big subreddit and the HN front page during PST business hours. Using Netlify or a service like it saves you having to administer and keep running an httpd, and “just add[s] a cdn in front”. It’s also free, and not $5.

is_true 5y ago

I do the same. Need to handle traffic? Cloudflare.

canyonero 5y ago

Netlify shines in a git based workflow with teams (deploy previews on every pull request, collaborative tools, etc). For a solo dev, I can understand the limited appeal if you already have a workflow that works for you.