dpl 1.5.2.travis.216.2 → 1.5.2.travis.217.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +8 -8
  2. data/README.md +116 -116
  3. metadata +1 -1
checksums.yaml CHANGED
@@ -1,15 +1,15 @@
1
1
  ---
2
2
  !binary "U0hBMQ==":
3
3
  metadata.gz: !binary |-
4
- Yzk3YzM5MDQ4M2FjZTk4Njg0MDVkN2M0MzQyZjc4MjNjNjYyZTA2NQ==
4
+ MjU4ODc2MTFiYmI2YjEyYzY0NzljNWJhMTZiYTcxNWNiMGNhMmI2ZA==
5
5
  data.tar.gz: !binary |-
6
- NWY3MDdhZTEzMGY4NTE0YzY2YjVjYjRhMWVkNTE3YTc2ZTZlZTQwMA==
6
+ NDYyODkzNzA0ZmEwNmJkNTI4ZjIzMDE3MmM3MDg5MjdhNjkwYTQ5NQ==
7
7
  !binary "U0hBNTEy":
8
8
  metadata.gz: !binary |-
9
- NTZhMmQxOWRkODNkYmQyOGMxNmRiNDIyOGQ5NjQ0N2Y4OTA2NjYxYmIzMTIw
10
- NTUzMTQzMjE0MTFhNDFiZjkzZDM2MDQ4Y2UxOGMzNTM4M2Y3ZTkxYWRhZmM4
11
- NzdiYjg0ZDFhMmJlMmRhNDhmYTBhNGU2NDZhZGE2Mjg4OGNiYTc=
9
+ MTY3YzQ3MjU0YjVjZTg3MjBlY2EwZjFjOWJhNzY1ODEyNTBkNDA0NDdmNGE5
10
+ ZjAyOGNlZjc1NTYwNzU3NDFiODU5ZWUyYjgwYmM2OWMwODdhNjc5NWJhNWNm
11
+ YTI5ZWNlMDMxYjA3MTNmMDhhYzY0NWI3YTJjMDg4MzYzMGIzODU=
12
12
  data.tar.gz: !binary |-
13
- OGY4ODJhMDlkODYwMjY3ZGRhMmNkMWVkMjg2ZTUyNzE4M2I4OTRiMWE5NzA0
14
- OThmNTA5NGFhN2VkNTg4OTI2NDY5N2Q3ZmRkYjI5MTA1ZmFiOTU1MTZkNzY0
15
- NGUyYzdiZDE2ODQxNTM0MjM2ZGM2MTliZDQ0Zjk3ZWVjM2E4ZTg=
13
+ OTRhYmViZTU0MGMzYjk4NzZhZTNjYTMxMjhjYzQ2OWJhMjc5ZmRjNTgwZjM4
14
+ MzkyZmM0YmNhOTIxMGQyNmIzOWM2ZGU2Y2U3YWI3MWFjOWQzN2NhNmNhZWQx
15
+ NGNkYjc1NzJmNDVkZDczZjE5NzZlOWRjZTdmNmFhMTQ2NGYyOWQ=
data/README.md CHANGED
@@ -1,173 +1,173 @@
1
- # Dpl [![Build Status](https://travis-ci.org/travis-ci/dpl.png?branch=master)](https://travis-ci.org/travis-ci/dpl]) [![Code Climate](https://codeclimate.com/github/travis-ci/dpl.png)](https://codeclimate.com/github/travis-ci/dpl)
2
- Dpl (dee-pee-ell) is a deploy tool made for continuous deployment. Developed and used by Travis CI.
3
-
4
- ## Supported Providers:
5
- Dpl supports the following providers:
6
-
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
-
20
- ## Installation:
21
-
22
- Dpl is published to rubygems.
23
-
24
- * Dpl requires ruby with a version greater than 1.8.7
25
- * To install: `gem install dpl`
26
-
27
- ## Usage:
28
-
29
- ###Security Warning:
30
-
31
- Running dpl in a terminal that saves history is insecure as your password/api key will be saved as plain text by it.
32
-
33
- ###Global Flags
34
- * `--provider=<provider>` sets the provider you want to deploy to. Every provider has slightly different flags, which are documented in the section about your provider following.
1
+ # Dpl [![Build Status](https://travis-ci.org/travis-ci/dpl.png?branch=master)](https://travis-ci.org/travis-ci/dpl]) [![Code Climate](https://codeclimate.com/github/travis-ci/dpl.png)](https://codeclimate.com/github/travis-ci/dpl)
2
+ Dpl (dee-pee-ell) is a deploy tool made for continuous deployment. Developed and used by Travis CI.
3
+
4
+ ## Supported Providers:
5
+ Dpl supports the following providers:
6
+
7
+ * [AppFog](#appfog)
8
+ * [Cloud Foundry](#cloud-foundry)
9
+ * [cloudControl](#cloudcontrol)
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
+
20
+ ## Installation:
21
+
22
+ Dpl is published to rubygems.
23
+
24
+ * Dpl requires ruby with a version greater than 1.8.7
25
+ * To install: `gem install dpl`
26
+
27
+ ## Usage:
28
+
29
+ ###Security Warning:
30
+
31
+ Running dpl in a terminal that saves history is insecure as your password/api key will be saved as plain text by it.
32
+
33
+ ###Global Flags
34
+ * `--provider=<provider>` sets the provider you want to deploy to. Every provider has slightly different flags, which are documented in the section about your provider following.
35
35
  * Dpl will deploy by default from the latest commit. Use the `--skip_cleanup` flag to deploy from the current file state. Note that many providers deploy by git and could ignore this option.
36
-
37
-
38
- ### Heroku:
39
-
40
- #### Options:
41
- * **api-key**: Heroku API Key
42
- * **strategy[git/anvil]**: Deployment strategy for Dpl. Defaults to anvil.
43
- * **app**: Heroku app name. Defaults to the name of your git repo.
44
- * **username**: heroku username. Not necessary if api-key is used. Requires git strategy.
45
- * **password**: heroku password. Not necessary if api-key is used. Requires git strategy.
46
-
47
- #### Git vs Anvil Deploy:
48
- * Anvil will run the [buildpack](https://devcenter.heroku.com/articles/buildpacks) compilation step on the Travis CI VM, whereas the Git strategy will run it on a Heroku dyno, which provides the same environment the application will then run under and might be slightly faster.
49
- * The Git strategy allows using *user* and *password* instead of *api-key*.
50
- * When using Git, Heroku might send you an email for every deploy, as it adds a temporary SSH key to your account.
51
-
52
- As a rule of thumb, you should switch to the Git strategy if you run into issues with Anvil or if you're using the [user-env-compile](https://devcenter.heroku.com/articles/labs-user-env-compile) plugin.
53
-
54
- #### Examples:
55
-
56
- dpl --provider=heroku --api-key=`heroku auth:token`
57
- dpl --provider=heroku --strategy=git --username=<username> --password=<password> --app=<application>
58
-
59
-
60
-
61
-
62
- ### Nodejitsu:
63
-
64
- #### Options:
65
-
36
+
37
+
38
+ ### Heroku:
39
+
40
+ #### Options:
41
+ * **api-key**: Heroku API Key
42
+ * **strategy[git/anvil]**: Deployment strategy for Dpl. Defaults to anvil.
43
+ * **app**: Heroku app name. Defaults to the name of your git repo.
44
+ * **username**: heroku username. Not necessary if api-key is used. Requires git strategy.
45
+ * **password**: heroku password. Not necessary if api-key is used. Requires git strategy.
46
+
47
+ #### Git vs Anvil Deploy:
48
+ * Anvil will run the [buildpack](https://devcenter.heroku.com/articles/buildpacks) compilation step on the Travis CI VM, whereas the Git strategy will run it on a Heroku dyno, which provides the same environment the application will then run under and might be slightly faster.
49
+ * The Git strategy allows using *user* and *password* instead of *api-key*.
50
+ * When using Git, Heroku might send you an email for every deploy, as it adds a temporary SSH key to your account.
51
+
52
+ As a rule of thumb, you should switch to the Git strategy if you run into issues with Anvil or if you're using the [user-env-compile](https://devcenter.heroku.com/articles/labs-user-env-compile) plugin.
53
+
54
+ #### Examples:
55
+
56
+ dpl --provider=heroku --api-key=`heroku auth:token`
57
+ dpl --provider=heroku --strategy=git --username=<username> --password=<password> --app=<application>
58
+
59
+
60
+
61
+
62
+ ### Nodejitsu:
63
+
64
+ #### Options:
65
+
66
66
  * **username**: Nodejitsu Username
67
- * **api-key**: Nodejitsu API Key
68
-
69
- #### Examples:
67
+ * **api-key**: Nodejitsu API Key
68
+
69
+ #### Examples:
70
70
  dpl --provider=nodejitsu --username=<username> --api-key=<api-key>
71
-
72
- ### Engine Yard:
73
-
74
- #### Options:
75
-
71
+
72
+ ### Engine Yard:
73
+
74
+ #### Options:
75
+
76
76
  * **api-key**: Engine Yard Api Key
77
- * **username**: Engine Yard username. Not necessary if api-key is used. Requires git strategy.
78
- * **password**: Engine Yard password. Not necessary if api-key is used.
79
- * **app**: Engine Yard Application name. Defaults to git repo's name.
77
+ * **username**: Engine Yard username. Not necessary if api-key is used. Requires git strategy.
78
+ * **password**: Engine Yard password. Not necessary if api-key is used.
79
+ * **app**: Engine Yard Application name. Defaults to git repo's name.
80
80
  * **environment**: Engine Yard Application Environment. Optional.
81
- * **migrate**: Engine Yard migration commands. Optional.
82
-
83
- #### Examples:
84
-
81
+ * **migrate**: Engine Yard migration commands. Optional.
82
+
83
+ #### Examples:
84
+
85
85
  dpl --provider=engineyard --api-key=<api-key>
86
86
  dpl --provider=engineyard --username=<username> --password=<password> --environment=staging
87
87
  dpl --provider=engineyard --api-key=<api-key> --app=<application> --migrate=`rake db:migrate`
88
-
88
+
89
89
  ### Openshift:
90
-
90
+
91
91
  #### Options:
92
-
92
+
93
93
  * **username**: Openshift Username.
94
94
  * **password**: Openshift Password.
95
95
  * **domain**: Openshift Application Domain.
96
96
  * **app**: Openshift Application. Defaults to git repo's name.
97
-
97
+
98
98
  ####Examples:
99
-
99
+
100
100
  dpl --provider=openshift --username=<username> --password=<password> --domain=<domain>
101
101
  dpl --provider=openshift --username=<username> --password=<password> --domain=<domain> --app=<app>
102
-
102
+
103
103
  ### cloudControl:
104
-
104
+
105
105
  #### Options:
106
-
106
+
107
107
  * **email**: cloudControll email.
108
108
  * **password**: cloudControll password.
109
109
  * **deployment**: cloudControll Deployment. Follows the format "APP_NAME/DEP_NAME".
110
-
110
+
111
111
  #### Examples:
112
-
112
+
113
113
  dpl --provider=cloudcontroll --email=<email> --password<password> --deployment=`APP_NAME/DEP_NAME`
114
-
114
+
115
115
  ### RubyGems:
116
-
116
+
117
117
  #### Options:
118
-
118
+
119
119
  * **api-key**: Rubygems Api Key.
120
-
120
+
121
121
  #### Examples:
122
-
122
+
123
123
  dpl --provider=rubygems --api-key=<api-key>
124
-
124
+
125
125
  ### PyPI:
126
-
126
+
127
127
  #### Options:
128
-
128
+
129
129
  * **user**: PyPI Username.
130
130
  * **password**: PyPI Password.
131
131
  * **server**: Optional. Only required if you want to release to a different index. Follows the form of "https://mypackageindex.com/index".
132
-
132
+
133
133
  #### Examples:
134
-
134
+
135
135
  dpl --provider=pypi --user=<username> --password=<password>
136
136
  dpl --provider=pypi --user=<username> --password=<password> --server=`https://mypackageindex.com/index`
137
-
137
+
138
138
  ### NPM:
139
-
139
+
140
140
  #### Options:
141
-
141
+
142
142
  * **email**: NPM email.
143
143
  * **api-key**: NPM api key. Can be retrieved from your ~/.npmrc file.
144
-
144
+
145
145
  #### Examples:
146
-
146
+
147
147
  dpl --provider=npm --email=<email> --api-key=<api-key>
148
-
148
+
149
149
  ### S3:
150
-
150
+
151
151
  #### Options:
152
-
153
- * **access-key-id**: AWS Access Key ID. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
152
+
153
+ * **access-key-id**: AWS Access Key ID. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
154
154
  * **secret-access-key**: AWS Secret Key. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
155
155
  * **bucket**: S3 Bucket.
156
-
156
+
157
157
  #### Examples:
158
-
158
+
159
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
+
163
163
  #### Options:
164
-
164
+
165
165
  * **email**: Appfog Email.
166
166
  * **password**: Appfog Password.
167
167
  * **app**: Appfog App. Defaults to git repo's name.
168
-
168
+
169
169
  #### Examples:
170
-
170
+
171
171
  dpl --provider=appfog --email=<email> --password=<password>
172
172
  dpl --provider=appfog --email=<email> --password=<password> --app=<app>
173
-
173
+
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: dpl
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.5.2.travis.216.2
4
+ version: 1.5.2.travis.217.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Konstantin Haase