ey-scp 0.2.0 → 0.3.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (5) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +1 -0
  3. data/bin/ey-scp +2 -1
  4. data/ey-scp.gemspec +1 -1
  5. metadata +9 -8
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: bb2d85190e06c4933ae2ee60aa0d7bf5a0721838
4
- data.tar.gz: 91a4c9132ea811b2fa3c32aa830643414c32c406
3
+ metadata.gz: 7043cce43a0e15a6ec8efde762c2b2d2614a344e
4
+ data.tar.gz: 166c391a5280060d7fc4b5cf8e3358778c38800b
5
5
  SHA512:
6
- metadata.gz: bf5d76cbf544e75a583a6ab97d4edb4715aa90c1aa125e83890b484456cc285f559f8bb8799fc87a37f5784856c9a4ffaeb43fdf8ec94855ea498eca4d14f720
7
- data.tar.gz: c5ff5872aeb35bb2a8a3a4cf05bd18acda02134a7e05b6261b421d456df1be746bf3022f5c7c4452e68e1779e421d5a6f4db77346022b027cc8a175669593176
6
+ metadata.gz: ec2db472b3ac1333a9b861d27e454c93792de0632073a401e68fa1e31f847d365c08070d7125f36fd01ab553bf104a2def9982b3a933db42734cb6399653bcc9
7
+ data.tar.gz: 688533e77e5e1ca3aef0657a8fd6527c9eeef766ad05a6928ea8b54609383838f250ec32ac8a69d08d42f896425e86fcd94cea9673c7aac98c049f98d43e97bc
data/README.md CHANGED
@@ -37,6 +37,7 @@ Option | Uploads to instances with roles of
37
37
  --db-servers | solo, db_master, db_slave
38
38
  --db-master | solo, db_master
39
39
  --db-slaves | solo, db_slave
40
+ --util-servers | solo, util
40
41
 
41
42
  ## Contributing
42
43
 
data/bin/ey-scp CHANGED
@@ -17,7 +17,8 @@ ROLES = {
17
17
  app_master: {flag: '--app-master', roles: ['solo', 'app_master'], title: 'application master'},
18
18
  db_servers: {flag: '--db-servers', roles: ['solo', 'db_master', 'db_slave'], title: 'database servers'},
19
19
  db_master: {flag: '--db-master', roles: ['solo', 'db_master'], title: 'database master'},
20
- db_slaves: {flag: '--db-slaves', roles: ['solo', 'db_slave'], title: 'database slaves'}
20
+ db_slaves: {flag: '--db-slaves', roles: ['solo', 'db_slave'], title: 'database slaves'},
21
+ util_servers: {flag: '--util-servers', roles: ['solo', 'util'], title: 'utility servers'}
21
22
  }
22
23
 
23
24
 
@@ -1,7 +1,7 @@
1
1
  # coding: utf-8
2
2
  Gem::Specification.new do |spec|
3
3
  spec.name = "ey-scp"
4
- spec.version = '0.2.0'
4
+ spec.version = '0.3.0'
5
5
  spec.authors = ["Steven Dunlap"]
6
6
  spec.email = ["steven@roadtrippers.com"]
7
7
  spec.description = "Quickly copy files (e.g. YMLs or configuration files) to multiple EngineYard servers"
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: ey-scp
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.0
4
+ version: 0.3.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Steven Dunlap
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2014-03-14 00:00:00.000000000 Z
11
+ date: 2014-07-15 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bundler
@@ -116,7 +116,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
116
116
  version: '0'
117
117
  requirements: []
118
118
  rubyforge_project:
119
- rubygems_version: 2.1.11
119
+ rubygems_version: 2.0.14
120
120
  signing_key:
121
121
  specification_version: 4
122
122
  summary: '# ey-scp Provides a CLI to quickly and painlessly deploy configuration
@@ -128,9 +128,10 @@ summary: '# ey-scp Provides a CLI to quickly and painlessly deploy configuratio
128
128
  /remote/project/path/config ### Specifying target instances Option | Uploads to
129
129
  instances with roles of ------ | ---------------------------------- --app-servers
130
130
  | solo, app_master, app --app-master | solo, app_master --db-servers | solo, db_master,
131
- db_slave --db-master | solo, db_master --db-slaves | solo, db_slave ## Contributing Right
132
- now, we could really use someone to refactor the code so that it''s less scripty/hackish. 1.
133
- Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit
134
- your changes (`git commit -am ''Add some feature''`) 4. Push to the branch (`git
135
- push origin my-new-feature`) 5. Create new Pull Request'
131
+ db_slave --db-master | solo, db_master --db-slaves | solo, db_slave --util-servers
132
+ | solo, util ## Contributing Right now, we could really use someone to refactor
133
+ the code so that it''s less scripty/hackish. 1. Fork it 2. Create your feature
134
+ branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am
135
+ ''Add some feature''`) 4. Push to the branch (`git push origin my-new-feature`)
136
+ 5. Create new Pull Request'
136
137
  test_files: []