dpl 1.5.2.travis.201.2 → 1.5.2.travis.206.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. checksums.yaml +8 -8
  2. data/README.md +28 -28
  3. metadata +2 -2
checksums.yaml CHANGED
@@ -1,15 +1,15 @@
1
1
  ---
2
2
  !binary "U0hBMQ==":
3
3
  metadata.gz: !binary |-
4
- MTIzYjgzNGJhODY2M2NjNGYxOWVmZGM3ZGM5MTA1NTEyZGNmMGI1NA==
4
+ MWFjYmJhYWNkNjk0M2Q2MjNiNzI4YjU2MTk3NmEyZDY3Yzc3ZDhiNQ==
5
5
  data.tar.gz: !binary |-
6
- MWI2M2ExYTkxMmI1MjE5MGM3OTM5ZGE1YjAxODkzY2JiMjNiM2EzZQ==
6
+ MTI4MDM3NWQ2NDg4ZTJlZjZhOWZhM2FkZjkyNTdhNWUxNzNkZGNjZA==
7
7
  !binary "U0hBNTEy":
8
8
  metadata.gz: !binary |-
9
- Zjc4MjY4NWNkYTBmZThlZWJlMjRkNmQyZWIzNmE2YmE0MjQwMzlhMDk1MWUw
10
- MTI1YzFiNzJjZDg2OTUzNDg3YzMxMjlmNWRhYmUyODc2ZDk3N2NlNGYyMmEx
11
- ZGIyNDA3OTQyMDg3M2Q2OGU0ZjRhNmE0NmZhZGM0Y2I3YzY4ZjI=
9
+ Y2RhNTIyMTA4N2ZjNzg0MzAyZGY4YmViZTQ0ZDgwNDVhOTA5ZmU4OTZlYzQ1
10
+ ZjEyODVkOTRlMWIyOGExMDcxZDI3ZDk4NjQzYTNjMmNmY2NkOGFiOTUwNWY2
11
+ ZGU2ODI0YzAxZTdlNjdkYzYxZmIxMGVjYzRjZTE2OTc3ODJlMjU=
12
12
  data.tar.gz: !binary |-
13
- YmYyNzc3ODU1ZmY0NWI1NzlhMGNjYTA0MTk2NDEzMjJhMjhjYjA5MWM0NWFj
14
- OTc4NzA3MGNmMTMxNjNjMGI2OGRhMDI5YWZjYzhhNDIyMDY2ODZkODhmZDA4
15
- MzkxYTljN2YzZjE3NjlhZTAxNDE5YTgxYzZhNmExM2FhN2VmOTY=
13
+ MTQwMDJhZDk3ZDNlYmI0ZDM3NDlkYmFkY2RkYWY0OWY3ZWVmMmMzZWUzOWMw
14
+ YmNkNTVlNTljZjcwZTVmNTg0MGFhNjFjMzIzZWI1MmFiNTQyMzVjMzVkMTdl
15
+ ZGIzNWM2ZjAwNGQyMTYzZTk4MzFiMzIzZTc0MjA0YjI5YTNiMWE=
data/README.md CHANGED
@@ -1,21 +1,21 @@
1
- # Dpl
1
+ # Dpl [![Build Status](https://travis-ci.org/travis-ci/dpl.png?branch=master)](https://travis-ci.org/travis-ci/dpl])
2
2
  Dpl (dee-pee-ell) is a deploy tool made for continuous deployment. Developed and used by Travis CI.
3
3
 
4
- ## Supported providers:
4
+ ## Supported Providers:
5
5
  Dpl supports the following providers:
6
6
 
7
- * AppFog
8
- * Cloud Foundry
9
- * cloudControl
10
- * dotCloud (experimental)
11
- * Engine Yard
12
- * Heroku
13
- * Nodejitsu
14
- * NPM
15
- * Openshift
16
- * PyPi
17
- * RubyGems
18
- * S3
7
+ * [AppFog](#appfog)
8
+ * [Cloud Foundry](#cloud-foundry)
9
+ * [cloudControl](#cloudcontroll)
10
+ * [dotCloud (experimental)](#dotcloud)
11
+ * [Engine Yard](#engine-yard)
12
+ * [Heroku](#heroku)
13
+ * [Nodejitsu](#nodejitsu)
14
+ * [NPM](#npm)
15
+ * [Openshift](#openshift)
16
+ * [PyPi](#pypi)
17
+ * [RubyGems](#rubygems)
18
+ * [S3](#s3)
19
19
 
20
20
  ## Installation:
21
21
 
@@ -54,7 +54,7 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
54
54
  #### Examples:
55
55
 
56
56
  dpl --provider=heroku --api-key=`heroku auth:token`
57
- dpl --provider=heroku --strategy=git --username=<username> --password=<password> --app=<application>
57
+ dpl --provider=heroku --strategy=git --username=<username> --password=<password> --app=<application>
58
58
 
59
59
 
60
60
 
@@ -67,7 +67,7 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
67
67
  * **api-key**: Nodejitsu API Key
68
68
 
69
69
  #### Examples:
70
- dpl --provider=nodejitsu --username=<username> --api-key=<api-key>
70
+ dpl --provider=nodejitsu --username=<username> --api-key=<api-key>
71
71
 
72
72
  ### Engine Yard:
73
73
 
@@ -82,9 +82,9 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
82
82
 
83
83
  #### Examples:
84
84
 
85
- dpl --provider=engineyard --api-key=<api-key>
85
+ dpl --provider=engineyard --api-key=<api-key>
86
86
  dpl --provider=engineyard --username=<username> --password=<password> --environment=staging
87
- dpl --provider=engineyard --api-key=<api-key> --app=<application> --migrate=`rake db:migrate`
87
+ dpl --provider=engineyard --api-key=<api-key> --app=<application> --migrate=`rake db:migrate`
88
88
 
89
89
  ### Openshift:
90
90
 
@@ -97,8 +97,8 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
97
97
 
98
98
  ####Examples:
99
99
 
100
- dpl --provider=openshift --username=<username> --password=<password> --domain=<domain>
101
- dpl --provider=openshift --username=<username> --password=<password> --domain=<domain> --app=<app>
100
+ dpl --provider=openshift --username=<username> --password=<password> --domain=<domain>
101
+ dpl --provider=openshift --username=<username> --password=<password> --domain=<domain> --app=<app>
102
102
 
103
103
  ### cloudControl:
104
104
 
@@ -110,7 +110,7 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
110
110
 
111
111
  #### Examples:
112
112
 
113
- dpl --provider=cloudcontroll --email=<email> --password<password> --deployment=`APP_NAME/DEP_NAME`
113
+ dpl --provider=cloudcontroll --email=<email> --password<password> --deployment=`APP_NAME/DEP_NAME`
114
114
 
115
115
  ### RubyGems:
116
116
 
@@ -120,7 +120,7 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
120
120
 
121
121
  #### Examples:
122
122
 
123
- dpl --provider=rubygems --api-key=<api-key>
123
+ dpl --provider=rubygems --api-key=<api-key>
124
124
 
125
125
  ### PyPI:
126
126
 
@@ -132,8 +132,8 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
132
132
 
133
133
  #### Examples:
134
134
 
135
- dpl --provider=pypi --user=<username> --password=<password>
136
- dpl --provider=pypi --user=<username> --password=<password> --server=`https://mypackageindex.com/index`
135
+ dpl --provider=pypi --user=<username> --password=<password>
136
+ dpl --provider=pypi --user=<username> --password=<password> --server=`https://mypackageindex.com/index`
137
137
 
138
138
  ### NPM:
139
139
 
@@ -144,7 +144,7 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
144
144
 
145
145
  #### Examples:
146
146
 
147
- dpl --provider=npm --email=<email> --api-key=<api-key>
147
+ dpl --provider=npm --email=<email> --api-key=<api-key>
148
148
 
149
149
  ### S3:
150
150
 
@@ -156,7 +156,7 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
156
156
 
157
157
  #### Examples:
158
158
 
159
- dpl --provider=s3 --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket>
159
+ dpl --provider=s3 --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket>
160
160
 
161
161
  ### Appfog:
162
162
 
@@ -168,6 +168,6 @@ As a rule of thumb, you should switch to the Git strategy if you run into issues
168
168
 
169
169
  #### Examples:
170
170
 
171
- dpl --provider=appfog --email=<email> --password=<password>
172
- dpl --provider=appfog --email=<email> --password=<password> --app=<app>
171
+ dpl --provider=appfog --email=<email> --password=<password>
172
+ dpl --provider=appfog --email=<email> --password=<password> --app=<app>
173
173
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: dpl
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.5.2.travis.201.2
4
+ version: 1.5.2.travis.206.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Konstantin Haase
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2013-11-02 00:00:00.000000000 Z
11
+ date: 2013-11-03 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rspec