calavera

Hi, CTO of Netlify here,

let us know if you need any help moving out docs, websites or any other web property from there, we'll be super happy to help. Projects like Kubernetes, Docker and React are already using our free offering for Open Source.

this webpack plugin might help you: https://gist.github.com/Kamshak/35630ec21df8dca27de3bb915f2d...

I have no idea why the original comment by the author is shadow banned.

I just deployed a change that we think it should fix the problem in your site, we're going to keep an eye on it \o/

Hey StavrosK, don't hesitate to reach out to Netlify support. I'd love to take a look at your site to figure out what's going on there.

Hi,

Netlify CTO here.

You're right, everything that the CMS does currently could also be done with raw Git messages. The CMS is designed to have pluggable backends. We had an early version working with Git directly. We decided to focus in one backend at a time rather than having several half integrated because the core features were evolving too fast to support several backends initially.

We plan on support raw Git in the future again. It's a matter of making sure it's useful for more people other than developers that already know how to use Git.

I agree with you, $10 in AWS fees sounds like a lot of traffic. That's also why Netlify has a free tier. We leave paid plans for people with more traffic. We event have a redundant DNS service for people that really really need it. For your needs is completely free of charge and hassle :)

PS: As I pointed below, I'm the CTO of Netlify.

that tutorial is pretty awesome, very well written.

Netlify can do everything you explain there by running one single command line. Check this video out: https://www.youtube.com/watch?v=IfFenanuRnc&feature=youtu.be

Netlify Pages is our free tier that offers a few things that GitLab Pages doesn't offer. For instance, we build merge requests for you and integrate them with commit statuses. So you get a real development workflow for your websites.

Check this blog posts out: https://www.netlify.com/blog/2016/07/20/introducing-deploy-p... https://www.netlify.com/blog/2016/08/30/introducing-deploy-c...

CloudFront is good. We use it for large assets. After managing thousands of sites, we realized that it's actually a hassle to manage cache invalidation yourself.

We work with several cloud providers to offer a better experience at the CDN level and manage caches for you. Our CDN also allows proxying end-to-end encrypted connections, so you can use it to host front-end apps and redirect requests to backend servers somewhere else.

Hi,

Netlify CTO here.

It's great that a combination of those services works for you. Our initial tier is completely free, $0. No costs per traffic nor storage, unlike S3.

Please, feel free to send questions and I'll be happy to answer them.

Thanks!

Signup permissions is definitely something we need to work on more. We optimized them at the beginning to give people the best experience possible, but we'll definitely iterate to allow using Netlify with less permissions. We just need to find the right workflow to still keep it as simple and powerful as possible.

Netlify CTO here (so I'm very biased).

These are some things that you can do with our Pages tier FREE, that you cannot do with GH Pages:

- We don't restrict people to only one static site generator, like Jekyll. You have use whatever with our Continuous Deployment.

- Automatic rollbacks at the CDN level. If you push a broken site, you don't need to stress about fixing the issue, pushing again, and waiting until the changes are published again. We have a big button that says "Rollback". Clicking that, our CDN automatically purges your site and promotes the good version you want. After that, you can spend as much time as you want writing a proper fix.

- Deploy Previews for Pull Requests hosted live. We build each pull request and put it in a subdomain so you can collaborate building sites much easily. Blog post announcement: https://www.netlify.com/blog/2016/07/20/introducing-deploy-p...

- Automatic provisioning and renewals of Let's Encrypt certificates for custom domains. If you have a custom domain, we do that for you, you don't have to worry about anything.

- Free custom domains, you have to have a paid subscription with GitHub if you want to use your own domain.

As I said again, those things are FREE with our initial plan, $0.

Happy to answer more questions if you have more.

Thanks Sid!

It was actually very easy to integrate. Thanks for making the API so easy to use.

being able to see pull requests deployed live without compromising production changed drastically the way we work as a team and we build our front-end applications. I can't wait to get other people's feedback.

we use d3 for all our charts.

Yes, the testing/deployment cycle for Enterprise is totally different. We usually release a major version with new features every two/three months, and 2 or 3 minor versions with bug fixes in between.

We always keep the version of github synchronized with master for development/testing, although we only release master directly in major releases. For minor releases we avoid to include major features from github to keep it as much stable as possible.