Browse files

[handbook] fixes some stuff

  • Loading branch information...
dscape committed Nov 30, 2012
1 parent 15963ef commit 14fa64cde0adad4161da462214a56290696569f1
Showing with 6 additions and 1 deletion.
  1. +6 −1 chapters/
@@ -1,3 +1,4 @@
+<a name="webhookapi-index"></a>
# Nodejitsu Web-hook API
Access the `Admin` section on your open source node.js Github repository. Click `Service Hooks` and then `Nodejitsu`. You will be presented with a form with four fields:
@@ -11,6 +12,7 @@ Access the `Admin` section on your open source node.js Github repository. Click
Select `Active` and hit `Update Settings`. From now on every-time you commit to Github (in the designated deployment branch) we will deploy that application for you. That simple.
+<a name="webhookapi-monitor"></a>
## Monitoring deployments
There's several ways to access the deployment status in the Nodejitsu Webhook API, and you can find the complete documentation at [](
@@ -40,6 +42,7 @@ Each request to our API is logged with a unique `uuid`, so you can use it to ref
We are now ready to deploy, go back to Github and click `Test Hook`. You should be up and running shortly.
+<a name="webhookapi-travis"></a>
## Travis
What about continuous integration? We added [Travis-CI]( so you can feel safe about your deployments. Simply add something like this in your `.travis.yml` file.
@@ -57,6 +60,7 @@ Internally our API will try to see if you have Travis configured like this, and
If tests failed we won't deploy. Simple.
+<a name="webhookapi-private_repos"></a>
## Deploying Private Repos & Commit Status API
If you authorize access so we can use your github account we can do more fun stuff like allowing you to deploy your private repositories, or even update your [commit status]( and check if a deployment worked directly in github.
@@ -68,10 +72,11 @@ To authorize simply do:
``` sh
curl -X POST \
-H "Content-type: application/json" \
- --data "{ \"credentials\": githubUser:githubPassword }" \
+ --data "{ \"credentials\": \"githubUser:githubPassword\" }" \
+<a name="webhookapi-apikeys_and_secret_stuff"></a>
## But wait, I have API keys I can't commit to Github as open source?!
Don't worry, you can use `jitsu set env` to set environment variables that you can access with `process.env`. Check our [handbook]( for more information. Environment variables set this way persist across deployments and are also available in our [webops]( application.

0 comments on commit 14fa64c

Please sign in to comment.