From 28f1b0b3a766fa70e792b364dafc7ab2ba36b38e Mon Sep 17 00:00:00 2001 From: Jordan Eldredge Date: Wed, 2 May 2018 08:52:31 -0700 Subject: [PATCH] Clean up deploy docs --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f766fbaa..f937b830 100755 --- a/README.md +++ b/README.md @@ -44,12 +44,11 @@ Open the local ip/port that is output to the console in your browser. ## Deploying -[Netlify](https://www.netlify.com/) watches GitHub for new versions of master. -When a new ve +[Netlify](https://www.netlify.com/) watches GitHub for new versions of master. When a new version is seen, it is automatically built using `npm run build` and pushed to the server. Additionally, Netlify will run a build on every pull request and include a link under the heading "Deploy preview ready!". This enables easy high level testing of pull requests. -[Travis](https://travis-ci.org/) runs the build and then pushes the contents of `./built` to the `gh-pages` branch of this repository. GitHub Pages then serve that directory as . CloudFlare sits in front of GitHub pages to provide the SSL certificate. +In short, deploying should be as simple as pushing a commit to master. -In short, deploying should be as simple as pushing a commit to master which builds, lints and passes all tests. +Additionally, if you want to fork the project, deploying should be as simple as setting up a free Netlify account. ### Advanced Usage