Nelitfy button added to the deploy section to README for starter

[bdougie]

Hey Kyle, Netlify created a new deploy to netlify button, which allows the user to test out the Gatsby template without cloning and spinning up gatsby. This PR is just including a button in the README.

Can you take a look this? Any feedback on this would be greatly appreciated.

[KyleAMathews]

I really like this idea but I don't think it's ready for primetime. When you click on screen, the instructions are a bit barebones. I can see people getting confused about what's going on. Things that standout:

• have name of "app" you're deploying in header instead of "new site" e.g. "Create new Gatsby Starter Default site on Netlify".
• replace "Clone gatsbyjs/gatsby-starter-default into your GitHub account." with something like "Clone gatsbyjs/gatsby-starter-default into a new repository in your GitHub account."
• then here copy Heroku's deploy button and start building but show the build logs inline (jumping to deploy page was odd)
• then once the build is done (or perhaps while it's building) explain how to get a local development environment setup and how when they push changes to github netlify will rebuild their site.

[KyleAMathews]

Also Yarn 17.10 is still having trouble installing Gatsby https://app.netlify.com/sites/cook-crocodile-63252/deploys/5848befd71e20a4b04e512bb

Perhaps 0.18 would fix that? https://github.com/yarnpkg/yarn/releases/tag/v0.18.0

[bdougie]

We are actively looking into solutions for the yarn timeouts. yarnpkg/yarn#2232

[J-O-H-N-P-A-U-L]

hey guys - any luck in resolving those yarn issues on netlify yet?
thanks! - jp

[bdougie]

@JPHUNTER The issue seems to be on Yarn's end but we are waiting for feedback on yarnpkg/yarn#2232.

Our current workaround at the moment requires the user to do the following:

At present, we auto-install your dependencies using yarn if we find yarn.lock - but it frequently hangs when the 'fsevents' (or other module not available for our architecture) is even optionally required. So you have a few choices to work around it until we (or the yarn maintainers) comes up with something permanent. Let me know if none of these work (and why) and I can try to come up with some other suggestion.

don't ship us a yarn.lock and we'll use npm to install
If you can easily exorcise fsevents from the required list in yarn.lock (essentially - it shouldn't be mentioned on its own only as an optional dependency - there should not be a stanza in yarn.lock just about fsevents) then your build should succeed. I've yet to find a "proper" way to get into this state though - removing the dependency with yarn doesn't seem to work, though editing yarn.lock by hand can work temporarily.
pin your Node.js version to 6.9.1. You use the default (Node stable) at 6.9.2 but we have pinned a fixed version of yarn to 6.9.1 that works fine.
You can set the node version in two different ways:

Add a .nvmrc to your repository. This will also tell any other developer using the repository which version of node it depends on. You can either set a specific version or just have a major version in the file, like the number 6 for the latest version of node 6.x
Set a NODE_VERSION environment variable. You can set this either while linking the repository or afterwards from the site settings screen in our UI. The value inside can be anything you would use with nvm.

This is not ideal which is why we are looking forward to hearing feedback from our open issue.

[bdougie]

@KyleAMathews and @JPHUNTER we are unblocked on yarn. Netlify is working on a post-modem on the issue and details on the solution to have out next week. Feel free to try out the button now.

[KyleAMathews]

Sweet!

Is there anyway btw, to see how many times a button is used? That'd be cool to make publically available perhaps even add it to the button itself.

[bdougie]

That is in our plans to do so eventually, stay tuned.

[KyleAMathews]

Cool! Gatsby 1.0 will have support for themes and this would be a great incentive for theme authors.

…

On Tue, Jan 3, 2017, 2:16 PM Brian Douglas ***@***.***> wrote: That is in our plans to do so eventually, stay tuned. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#24 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEVh1BbMa5EWVb-9aFQr3pwPQpXOCYzks5rOrqrgaJpZM4LEzVQ> .