railsless-deploy 1.0.0 → 1.0.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.
- data/README.markdown +6 -6
- data/VERSION +1 -1
- data/lib/railsless-deploy.rb +2 -3
- metadata +12 -5
data/README.markdown
CHANGED
@@ -4,15 +4,15 @@ If you want to get the most out of Capistrano and you do not want to have to dea
|
|
4
4
|
|
5
5
|
## Installation
|
6
6
|
|
7
|
-
# gem
|
8
|
-
# gem install leehambley-railsless-deploy
|
7
|
+
# gem install railsless-deploy
|
9
8
|
|
10
|
-
## Usage
|
9
|
+
## Bundler Usage
|
10
|
+
|
11
|
+
As of bundler 0.9 you should use `:require => nil` when listing this gem in your Gemfile.
|
11
12
|
|
12
|
-
|
13
|
+
## Usage
|
13
14
|
|
14
|
-
|
15
|
-
# Dir['vendor/plugins/*/recipes/*.rb'].each { |plugin| load(plugin) }
|
15
|
+
Open your application's `Capfile` and make it begins like this:
|
16
16
|
|
17
17
|
require 'rubygems'
|
18
18
|
require 'railsless-deploy'
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
1.0.
|
1
|
+
1.0.2
|
data/lib/railsless-deploy.rb
CHANGED
@@ -43,7 +43,7 @@ Capistrano::Configuration.instance(:must_exist).load do
|
|
43
43
|
|
44
44
|
_cset :version_dir, "releases"
|
45
45
|
_cset :shared_dir, "shared"
|
46
|
-
_cset :shared_children,
|
46
|
+
_cset :shared_children, [] # Empty!
|
47
47
|
_cset :current_dir, "current"
|
48
48
|
|
49
49
|
_cset(:releases_path) { File.join(deploy_to, version_dir) }
|
@@ -145,14 +145,13 @@ Capistrano::Configuration.instance(:must_exist).load do
|
|
145
145
|
|
146
146
|
namespace :deploy do
|
147
147
|
desc <<-DESC
|
148
|
-
Deploys your project.
|
148
|
+
Deploys your project. Handy wrapper to hook into the beginning of the deployment. Note that \
|
149
149
|
this will generally only work for applications that have already been deployed \
|
150
150
|
once. For a "cold" deploy, you'll want to take a look at the `deploy:cold' \
|
151
151
|
task, which handles the cold start specifically.
|
152
152
|
DESC
|
153
153
|
task :default do
|
154
154
|
update
|
155
|
-
# restart
|
156
155
|
end
|
157
156
|
|
158
157
|
desc <<-DESC
|
metadata
CHANGED
@@ -1,7 +1,12 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: railsless-deploy
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
|
4
|
+
prerelease: false
|
5
|
+
segments:
|
6
|
+
- 1
|
7
|
+
- 0
|
8
|
+
- 2
|
9
|
+
version: 1.0.2
|
5
10
|
platform: ruby
|
6
11
|
authors:
|
7
12
|
- Lee Hambley
|
@@ -9,7 +14,7 @@ autorequire:
|
|
9
14
|
bindir: bin
|
10
15
|
cert_chain: []
|
11
16
|
|
12
|
-
date:
|
17
|
+
date: 2010-04-22 00:00:00 +02:00
|
13
18
|
default_executable:
|
14
19
|
dependencies: []
|
15
20
|
|
@@ -43,18 +48,20 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
43
48
|
requirements:
|
44
49
|
- - ">="
|
45
50
|
- !ruby/object:Gem::Version
|
51
|
+
segments:
|
52
|
+
- 0
|
46
53
|
version: "0"
|
47
|
-
version:
|
48
54
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
49
55
|
requirements:
|
50
56
|
- - ">="
|
51
57
|
- !ruby/object:Gem::Version
|
58
|
+
segments:
|
59
|
+
- 0
|
52
60
|
version: "0"
|
53
|
-
version:
|
54
61
|
requirements: []
|
55
62
|
|
56
63
|
rubyforge_project:
|
57
|
-
rubygems_version: 1.3.
|
64
|
+
rubygems_version: 1.3.6
|
58
65
|
signing_key:
|
59
66
|
specification_version: 3
|
60
67
|
summary: Replacement for the default Capistrano tasks, designed to make life easier for PHP/Perl/Python developers
|