Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

[minor fix] help our users dont keep stuff in bashhistory

  • Loading branch information...
commit dc9e22875152de61583c80c952828d5b40deb5aa 1 parent 4f4d29a
@dscape dscape authored
View
12 content/articles/features/webhooks.md
@@ -20,7 +20,7 @@ The most fun way to monitor your deployment is with the realtime status changes
``` bash
# if your username is foo and password is bar this would be
# https://foo:bar@webhooks.nodejitsu.com/1/status/foo/changes
-curl https://username:password@webhooks.nodejitsu.com/1/status/username/changes?include_docs=auto
+curl -u username https://webhooks.nodejitsu.com/1/status/username/changes?include_docs=auto
```
This will create an HTTP keep alive connection that pushes the status to you in realtime every time someone invokes our API:
@@ -97,7 +97,7 @@ Check [Sample Payloads](#payloads) for examples. This method is normally called
You must configure the github webhook to use the travis webhook. Works under the assumption that if your repository has a `.travis.yml` file and that contains at least one webhook notification we shouldn't deploy from the github request, but instead wait until travis triggers the notify event and calls our API. This effectively means that if travis tests don't pass your application does not get deployed.
```
-curl -X POST -d @file https://user:pass@webhooks.nodejitsu.com/1/deploy
+curl -X POST -u username -d @file https://webhooks.nodejitsu.com/1/deploy
```
Authentication can use a pair of `user:pass` or `user:apiToken`.
@@ -204,7 +204,7 @@ GET /1/status/:user/webhooks/:application
Gets the install status for a specific user. Useful to determine if the deploy worked, or why it failed. `:user` is your nodejitsu username and `:application` is your application name.
```
-curl https://dscape:password@webhooks.nodejitsu.com/1/status/dscape/webhooks/hello-world-api-flatiron?limit=10\&skip=20
+curl -u dscape https:/webhooks.nodejitsu.com/1/status/dscape/webhooks/hello-world-api-flatiron?limit=10\&skip=20
```
<a name="status-qs"></a>
@@ -306,7 +306,7 @@ GET /1/status/:user/changes/:id
Streams log files as you deploy application with a changes stream. When you provide an id it will just return that entry and close the http connection.
```
-curl https://dscape:password@webhooks.nodejitsu.com/1/status/dscape/changes?include_docs=true
+curl -u dscape https://webhooks.nodejitsu.com/1/status/dscape/changes?include_docs=true
```
<a name="changes-qs"></a>
@@ -402,7 +402,9 @@ POST /1/auth/github
Tries to get authorization from github, so elevated privileges can be used on that service. This will give us access to get working code from your repositories and change the status of a specific pull request
```
-curl -X POST nodejitsuUser:nodejitsuPwd@webhooks.nodejitsu.com/1/auth/github --data '{"credentials":"githubUser:githubPass"}' --header "Content-type: application/json"
+curl -X POST -u nodejitsuUser https://webhooks.nodejitsu.com/1/auth/github \
+ --data '{"credentials":"githubUser:githubPass"}' \
+ --header "Content-type: application/json"
```
<a name="auth-qs"></a>
View
12 public/features/webhooks.html
@@ -142,7 +142,7 @@ <h1 class="title">Continuous Deployment</h1>
</p>
<pre><code class="lang-bash"><span class="comment"># if your username is foo and password is bar this would be </span>
<span class="comment"># https://foo:bar@webhooks.nodejitsu.com/1/status/foo/changes</span>
-curl https://username:password@webhooks.nodejitsu.com/1/status/username/changes?include_docs=auto</code></pre>
+curl -u username https://webhooks.nodejitsu.com/1/status/username/changes?include_docs=auto</code></pre>
<p>This will create an HTTP keep alive connection that pushes the status to you in realtime every time someone invokes our API:
</p>
@@ -217,7 +217,7 @@ <h1 class="title">Continuous Deployment</h1>
<p>You must configure the github webhook to use the travis webhook. Works under the assumption that if your repository has a <code>.travis.yml</code> file and that contains at least one webhook notification we shouldn&#39;t deploy from the github request, but instead wait until travis triggers the notify event and calls our API. This effectively means that if travis tests don&#39;t pass your application does not get deployed.
</p>
-<pre><code>curl -X POST -d @file https://user:pass@webhooks.nodejitsu.com/1/deploy</code></pre>
+<pre><code>curl -X POST -u username -d @file https://webhooks.nodejitsu.com/1/deploy</code></pre>
<p>Authentication can use a pair of <code>user:pass</code> or <code>user:apiToken</code>.
</p>
@@ -320,7 +320,7 @@ <h1 class="title">Continuous Deployment</h1>
<p>Gets the install status for a specific user. Useful to determine if the deploy worked, or why it failed. <code>:user</code> is your nodejitsu username and <code>:application</code> is your application name.
</p>
-<pre><code>curl https://dscape:password@webhooks.nodejitsu.com/1/status/dscape/webhooks/hello-world-api-flatiron?limit=10\&amp;skip=20</code></pre>
+<pre><code>curl -u dscape https:/webhooks.nodejitsu.com/1/status/dscape/webhooks/hello-world-api-flatiron?limit=10\&amp;skip=20</code></pre>
<p><a name="status-qs"></a>
</p>
<h4>Query String Parameters</h4>
@@ -417,7 +417,7 @@ <h1 class="title">Continuous Deployment</h1>
<p>Streams log files as you deploy application with a changes stream. When you provide an id it will just return that entry and close the http connection.
</p>
-<pre><code>curl https://dscape:password@webhooks.nodejitsu.com/1/status/dscape/changes?include_docs=true</code></pre>
+<pre><code>curl -u dscape https://webhooks.nodejitsu.com/1/status/dscape/changes?include_docs=true</code></pre>
<p><a name="changes-qs"></a>
</p>
<h4>Query String Parameters</h4>
@@ -508,7 +508,9 @@ <h1 class="title">Continuous Deployment</h1>
<p>Tries to get authorization from github, so elevated privileges can be used on that service. This will give us access to get working code from your repositories and change the status of a specific pull request
</p>
-<pre><code>curl -X POST nodejitsuUser:nodejitsuPwd@webhooks.nodejitsu.com/1/auth/github --data &#39;{&quot;credentials&quot;:&quot;githubUser:githubPass&quot;}&#39; --header &quot;Content-type: application/json&quot;</code></pre>
+<pre><code>curl -X POST -u nodejitsuUser https://webhooks.nodejitsu.com/1/auth/github \
+ --data &#39;{&quot;credentials&quot;:&quot;githubUser:githubPass&quot;}&#39; \
+ --header &quot;Content-type: application/json&quot;</code></pre>
<p><a name="auth-qs"></a>
</p>
<h4>Query String Parameters</h4>
Please sign in to comment.
Something went wrong with that request. Please try again.