dpl 1.8.31.travis.1895.3 → 1.8.31.travis.1897.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 62f3ea41a9c26f90c38fc44979e14f4b33f7634e
-  data.tar.gz: a1086c77b7ee5a46802e0e6005b13cbfeb856f84
+  metadata.gz: 5649d2e4ca1db9e7eb626ed8ca6edd837a938a05
+  data.tar.gz: f308e33667f12c71dba5b15cfcb9dfda63c5b6d6
 SHA512:
-  metadata.gz: b67d0361f56dcc47819fd18a73cf86515dd0af05647cf83a2f38415d80976f684756e6b4b1c3cffab9fd89d0f94755b57c8e485f0e3102da9ed54f59a63a38b7
-  data.tar.gz: 70f3889be7a53aea8a47b2d5d7455cf5b3700662537fac1c4a0b404615e43b3dce9504cfce5d19e036ac8c64bb1abe9c6950f501c4658d06c0e50dc899f87015
+  metadata.gz: 1318e7a9035efdb217d1df12367813b0945f56ba66eae83264d0e1cd0b5faeee436dbfa167f2a7cdfc5b0f45ccb608101334880da45e647ed8db516d648b7458
+  data.tar.gz: 8a60ecddd5b6f7dc9dc5ba5fb7367c0106e02b8fe862ed9ccbafeb78f2682db55cf337bd64020a4c623d07e896e24956a8e0db67983c2994b8ef446bcd015c0b

data/README.md

@@ -666,19 +666,20 @@ For accounts using two factor authentication, you have to use an oauth token as
 #### Setup:
 
 1. Get the deployment target for Catalyze:
-a. Make sure your catalyze environment is [associated](https://resources.catalyze.io/paas/paas-cli-reference/#associate).
-b. Get the git remote by running ```git remote -v``` from within the associated repo.
+  1. Make sure your catalyze environment is [associated](https://resources.catalyze.io/paas/paas-cli-reference/#associate).
+  2. Get the git remote by running ```git remote -v``` from within the associated repo.
 2. Setup a deployment key to Catalyze for Travis CI:
-a. Install the travis-ci cli.
-b. Get the public SSH key for your travis project and save it to a file by running ```travis pubkey > travis.pub```
-c. Add the key as a deploy key using the catalyze cli within the associated repo. For example:  ```catalyze deploy-keys add travisci ./travis.pub code-1```
+  1. Install the travis-ci cli.
+  2. Get the public SSH key for your travis project and save it to a file by running ```travis pubkey > travis.pub```
+  3. Add the key as a deploy key using the catalyze cli within the associated repo. For example:  ```catalyze deploy-keys add travisci ./travis.pub code-1```
 3. Setup Catalyze as a known host for Travis CI:
-a. List your known hosts by running ```cat ~/.ssh/known_hosts```
-b. Find and copy the line from known_hosts that includes the git remote found in step #1. It'll look something like "[git.catalyzeapps.com]:2222 ecdsa-sha2-nistp256 BBBB12abZmKlLXNo..."
-c. Update your `before_deploy` step in `.travis.yml` to update the `known_hosts` file:
-```
-    before_deploy:  echo "[git.catalyzeapps.com]:2222 ecdsa-sha2-nistp256 BBBB12abZmKlLXNo..." >> ~/.ssh/known_hosts
-```
+  1. List your known hosts by running ```cat ~/.ssh/known_hosts```
+  2. Find and copy the line from known_hosts that includes the git remote found in step #1. It'll look something like "[git.catalyzeapps.com]:2222 ecdsa-sha2-nistp256 BBBB12abZmKlLXNo..."
+  3. Update your `before_deploy` step in `.travis.yml` to update the `known_hosts` file:
+
+  ```
+  before_deploy:  echo "[git.catalyzeapps.com]:2222 ecdsa-sha2-nistp256 BBBB12abZmKlLXNo..." >> ~/.ssh/known_hosts
+  ```
 
 ### Chef Supermarket:
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dpl
 version: !ruby/object:Gem::Version
-  version: 1.8.31.travis.1895.3
+  version: 1.8.31.travis.1897.3
 platform: ruby
 authors:
 - Konstantin Haase