3 ms·

This looks great. Definitely going to give this a test run this weekend. A few questions: * What are the advantages of having the build on Netlify's end vs.

This looks great. Definitely going to give this a test run this weekend. A few questions: * What are the advantages of having the build on Netlify's end vs. the approach used in Divshot (build locally then deploy)? (I imagine the answer is the same as why you would setup a build server for your compiled codebase - repeatable + reproducible builds, etc. Just wondering if there are other reasons I may not be aware of) * What is the recommended workflow for setting up a beta environment and then promoting to a prod environment after testing? Would you use git branches for this?

bobfunk 12y ago
Awesome, do let us know any feedback you have once you try it out! You can do manual deploys (both from CLI and via drag'n drop) with netlify as well, and when you're prototyping or just throwing something online quickly, that's great. However, once you're working on a production project, it's very nice to know, that at any time what's in the master git branch actually represents the current live version of the site. When doing manual deploys, it's too easy to forget to pull/push before deploying. Apart from that, automated deploys opens up a bunch of new possibilities. Carrot have a pretty awesome post about using netlify with contentful (http://carrot.is/coding/static_cms http://carrot.is/coding/static_cms), and we're using it to automatically update https://www.staticgen.com https://www.staticgen.com once a day. For production/staging/dev envs, we recommend using branches yes. You can easily setup different sites to deploy from different branches, and the CLI tool have a -e flag as well, that makes it easy to work with different environments.