whiskey_disk 0.4.3 → 0.4.4

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.
data/README.markdown CHANGED
@@ -33,10 +33,15 @@ current local checkout.
33
33
  - You can do multi-project deployments, specifying deployment data in a single
34
34
  deploy.yml config file, or keep an entire directory of project deployment config files.
35
35
 
36
+ - You can separate per-deployment application configuration information (e.g., passwords,
37
+ database configs, hoptoad/AWS/email config data, etc.) in separate repositories from
38
+ the application, and whiskey\_disk will merge the correct data onto the deployed
39
+ application at deployment time.
40
+
36
41
  - You can have per-developer configurations for targets (especially
37
42
  useful for "local" or "development" targets). Use .gitignore, or
38
- specify a config_branch and everyone can have their own local setup that just
39
- works.
43
+ specify a config_branch and everyone can have their own local setup that just
44
+ works.
40
45
 
41
46
  - There's no before\_after\_before_after hooks. You've got plenty of
42
47
  flexibility with just a handful of rake hook points to grab onto.
@@ -74,7 +79,7 @@ As a rails plugin:
74
79
  ### Configuration ###
75
80
 
76
81
  - look in the examples/ directory for sample configuration files
77
- - main configuration is in %lt;app_root>/config/deploy.yml
82
+ - main configuration is in <app_root>/config/deploy.yml
78
83
  - config files are YAML, with a section for each target.
79
84
 
80
85
  Known config file settings (if you're familiar with capistrano and vlad these should seem eerily familiar):
data/TODO.txt CHANGED
@@ -1,4 +1,4 @@
1
- Q - how do we track registries of deployment files (do we recommend people use larry/puppet or is something else going on?)
1
+ - allow whiskey_disk to pull configuration file from an url (which would be based on project, environment)
2
2
 
3
3
  - do git-deploy style change detection:
4
4
  - get the current branch ref, then do the fetch/reset, get the current branch ref; find the differences, make them available to the rake task(s)
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.4.3
1
+ 0.4.4
data/whiskey_disk.gemspec CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  Gem::Specification.new do |s|
7
7
  s.name = %q{whiskey_disk}
8
- s.version = "0.4.3"
8
+ s.version = "0.4.4"
9
9
 
10
10
  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
11
11
  s.authors = ["Rick Bradley"]
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: whiskey_disk
3
3
  version: !ruby/object:Gem::Version
4
- hash: 9
4
+ hash: 7
5
5
  prerelease: false
6
6
  segments:
7
7
  - 0
8
8
  - 4
9
- - 3
10
- version: 0.4.3
9
+ - 4
10
+ version: 0.4.4
11
11
  platform: ruby
12
12
  authors:
13
13
  - Rick Bradley