[_fool]

I work for Netlify.

You don't have to use any of our clients to deploy a site; they're just options in case you'd rather build the site yourself than have us build it. I rarely use the clients (we have one in go in addition to the Node.js version: https://github.com/netlify/netlify-go and further our API is scriptable in any language and fully documented here: https://open-api.netlify.com/)

You can (and we do this for you by default) configure GitHub, GitLab, or Bitbucket to trigger a build whenever you do something at the repo. The default, free behavior builds on pushes or PR's against your selected branch and if it's a PR, shows you a deploy preview rather than publishing at your main URL: https://www.netlify.com/blog/2016/07/20/introducing-deploy-p...).

Finally you can drag and drop a zipfile with your site's built contents, if you are in a hurry or less technically inclined.

So, you don't need Node to use us and I don't think most of our customers do use that client; most build direct from their repositories.

[StavrosK]

Thank you, I'm one of those impossible customers who goes "oh I want a free tier, and oh, I don't like node, and oh, I don't want to give you access to my Gitlab", but it's great that you have a Go version of the client. I think I'm going to switch everything to you, I've been wanting to for a while!

[_fool]

awesome to hear! I'm the guy you'll talk to if you have a support question, so I hope to not hear from you soon (since that would mean that everything worked as expected :))

[StavrosK]

I'm sorry you had to hear from me, but I recant! Netlify is, indeed, fantastic. It took five minutes to move my site over, and fifteen minutes to waste Chris' time with questions.

I'm amazed at how fast the site is now: https://portfolio.stavros.io/

[_fool]

oops, I linked our Go library not our go client. You'll want https://github.com/netlify/netlifyctl for the client!