Re:Comparing Static Site Hosts; Which Is the Best Host for a...
by kevincox on Tuesday February 28, 2023 @09:07AM
(#34969421)
Yeah, I do sometimes use Netlify because it is so simple to set up. And you can deploy by POSTing them a zip archive which is quite a convenient API.
It largely makes up for their really basic build environment. Last I tried it you can basically pick between Ubuntu versions with some pre-installed software. If you wanted to use an unavailable tool you could either manually download it or you were out of luck.
Re:Comparing Static Site Hosts; Which Is the Best Host for a...
by sfmike on Tuesday February 28, 2023 @09:02AM
(#34969371)
might sound crazy but I still love drag and drop a whole Dir into netlify still, its a beautiful method using a computer mouse and it works quite well and takes seconds.
Re:Comparing Static Site Hosts; Which Is the Best Host for a...
by robertlagrant on Tuesday February 28, 2023 @09:06AM
(#34969411)
Reminds me of what I used to do 25 years ago with FTP :)
Re:Comparing Static Site Hosts; Which Is the Best Host for a...
by szundi on Tuesday February 28, 2023 @09:57AM
(#34969941)
... into Windows Commander :)
Re:Comparing Static Site Hosts; Which Is the Best Host for a...
by dp-hackernews on Tuesday February 28, 2023 @10:16AM
(#34970208)
...or Double Commander
Re:Comparing Static Site Hosts; Which Is the Best Host for a...
by cheesegradient on Tuesday February 28, 2023 @12:16PM
(#34971906)
I used to do that, but recently decided to try out deployment using Netlify CLI—and quickly decided never to drag-and-drop again, if I can help it! Now all I do is `make dev`, and if it looks good, `make netlify-deploy-prod`. Even faster than opening Netlify, going to the site, going to Deploy, and dragging and dropping. But I’m glad that it’s still an option, if I need it.
Re:Comparing Static Site Hosts; Which Is the Best Host for a...
by have_faith on Tuesday February 28, 2023 @09:43AM
(#34969786)
I've done both on Vercel. Their git repo connections can run basic CI for you on commits to certain branches etc. But you can also just use their CLI as part of your own CI process to deploy to them.
When I surveyed static hosting providers about a year ago, the only ones I found that didn't insist on taking over your CI pipeline were Netlify[0] and Firebase. I assume it's possible on Cloudflare and AWS, too, but I wanted to go with a provider where static hosting is core to their business.
I've been happy with Netlify, but given how deeply they bury their "manual deploy" feature, I fear the day that they decide to force everyone into the Netlify-native build workflow.
[0] https://docs.netlify.com/cli/get-started/#manual-deploys