Live data from Hacker News

Netlify Dev

netlify.com

231–237 of 237 posts

Re: Netlify Dev

#231
post #230
post #139

Earlier quoted context omitted.

As someone who works in the amorphous realm of "digital strategy", I was pursuing this exact "learning path" by deploying my personal website on Digital Ocean, where your droplet is a blank slate, and you have to configure everything. Given the number of help threads and spotty documentation I had to look through to deploy a simple Wordpress site, I'd say it was more of a hassle than anything else. Unless you plan on…

Not to turn a Netlify topic into a DigitalOcean topic, but when you created your droplet did you select the pre-built Wordpress option? May have helped you a bit. (I used dokku-wordpress[0] on my dokku imaged server, personally.) -- 0. https://github.com/dokku-community/dokku-wordpress

I did not, specifically because I wanted to learn how DO worked, without any "Wordpress 1-click wizard" stuff. Bluehost has the same "Instant Wordpress" thing that I avoid, as I write my own CSS and page templates and I wasn't planning to use an off-the-shelf theme.

On DO, I learned that you have to set up everything yourself, like SSH, Apache, MySQL, PHP, SFTP. I haven't found good documentation on how to set up a Git workflow from my local dev environment, so that's the next step. I have a non-database PHP site I plan to use for that.

Re: Netlify Dev

#232

Netlify is amazing: 1. Free 2. Good support 3. Custom domains with SSL 4. Takes care of most important backend stuff (forms and webhooks) 5. Functions (Lambda with zero config needed) 6. Abstracts server stuff like [redirects]( https://www.netlify.com/docs/redirects/ ) Lambda and redirects are the best. I can just put my scripts in a folder and they automagically work. In my LinkedIn profile my website address is not…

> 1. Free ... 4. Takes care of most important backend stuff (forms and webhooks) From my reading of https://www.netlify.com/pricing/#forms you will need to pay $19/month/site (!) just to collect the data from 1000 form submissions. By the time you have a couple of sites like this the price is already way too much for me and anyone else with basic backend knowledge. I hope I've misunderstood.

It makes the form features useless for hosting websites for non profits organizations and campaigns (which is a perfect use case for a static website).

Re: Netlify Dev

#233

Netlify is amazing: 1. Free 2. Good support 3. Custom domains with SSL 4. Takes care of most important backend stuff (forms and webhooks) 5. Functions (Lambda with zero config needed) 6. Abstracts server stuff like [redirects]( https://www.netlify.com/docs/redirects/ ) Lambda and redirects are the best. I can just put my scripts in a folder and they automagically work. In my LinkedIn profile my website address is not…

I decided I’m building and hosting my dev blog on Netlify now instead of anywhere else. This post honestly helped me get there.

Re: Netlify Dev

#234
post #202

Earlier quoted context omitted.

Honestly? Most internet sites don't _need_ a database. You could probably replace most* wordpress/squarespace/wix sites with a statically generated site. You can call api's from JS and host your database separately, also possible that people use some kind of "serverless" database like google firebase.

Most internet sites don't _need_ a database. Right, and the rest of them—a very significant portion—do. And yes, I realize that it's possible to use JS to fetch from anywhere, but what I'm wondering is what people are thinking when talking about Netlify. Are they thinking that this isn't really for database-backed websites but can be used if some other Netlify advantage justifies putting your database and the server…

I guess they're going after the people who don't need a db first, then add features to support some kind of "db-lite" functionality later. They're competing with wordpress/squarespace, not gcloud or aws (mostly..) :)

See addons: https://www.netlify.com/products/

Also services like this allow you to have a "cms" which is the typical use of a db for _most_ websites: https://www.contentful.com/.

You are correct, heavy db users probably wouldn't go with a service like this :)

Re: Netlify Dev

#235

Earlier quoted context omitted.

I don't like to use the term "static" site, even as a provider of a static site hosting service. I think when people say "static" they imagine a small site that does not change. I prefer to see it as a build environment for your code, data, and assets. The data can change all the time, but it either changes as part of a build process or pulled from an external API. Here's a good summary of a team choosing this approa…

In Netlify's case, does that mean there is no backend? No DB or node server?

Well, all the front-end code is precompiled and published to CDN. So at least from that perspective, there is continuously running server. Node would compile, publish, and cease to exist. The DB would have to be hosted elsewhere and made available via an API.

Re: Netlify Dev

#236

Earlier quoted context omitted.

What's your setup like? I've been looking around to set something like this up, mainly for being able to do quick fixes on the go. (Or use my iPad when I'm on holiday)

Unfortunately I don't have much to share because my setup is so simple. Literally just vim (you can find really awesome vimrc on GitHub, mines pretty messy), and tmux (simple apt install). When I visit my friends place I usually just use their computer, otherwise I'll use my MacBook pro or desktop. I don't think about setup much, I just use whatever devices around me to access and write code on my server instance.

Understood, for my purposes I was really looking for a more full-fletched dev environment. Being able to run a local dev server and a browser (for front-end dev). Sadly that doesn't seem to be possible on an iPad at the moment.

Re: Netlify Dev

#237
post #197

Earlier quoted context omitted.

> One feature I haven't seen in the comments here is the ability to just drag and drop an entire website folder from your harddisk to Netlify and it's live within seconds. Which worked great for a couple of older personal websites I had. How is this different than `aws s3 sync local/ s3://your-website.com`?

1. With Netlify you don't need to install any command line tool. For non-technical users it's a must. 2. Netlify is a CDN, so "dragging and dropping" would be equivalent to setting up S3 + Cloudfront. 3. You have to create the bucket before running this command. With Netlify you just drag and drop and it takes a couple seconds (if the site is small enough to be built that fast). 4. Netlify is also able to run a build…

npm install netlify-cli -g
Post reply on HN