capistrano-safe-deploy-to 1.0.0 → 1.1.0
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.
- checksums.yaml +4 -4
- data/README.md +14 -1
- data/lib/capistrano/safe_deploy_to/version.rb +1 -1
- data/lib/capistrano/tasks/safe_deploy_to.rake +1 -0
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 4067ff9a4666cfc72247eb29bfd932ab04a37367
|
|
4
|
+
data.tar.gz: c9e7f15a678e62e806f71c139aa344345bf78ace
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 813e2bec7e5055e50e4177fde1a11dd2d95461d5a26946210a875e4b459929801c5630bcc70cbea654153edce6ccb75f7c0ed9bcd932ff5e349840364461b474
|
|
7
|
+
data.tar.gz: c462ec3f12b9e1d67ac62bb8a3c18989d366329feed4362ca43fb7e95786c02baf566d760578da58f8176097b9a69d944f1b68065385e7154d09c267e355434b
|
data/README.md
CHANGED
|
@@ -25,7 +25,7 @@ That is easy to fix, right? A quick:
|
|
|
25
25
|
- `sudo mkdir -p /var/www/app_name`
|
|
26
26
|
- `sudo chown deploy:deploy /var/www/app_name`
|
|
27
27
|
|
|
28
|
-
Except that is painful, unnecessary and
|
|
28
|
+
Except that is painful, unnecessary and there's no need to manually `ssh` to the
|
|
29
29
|
server to deploy apps!
|
|
30
30
|
|
|
31
31
|
There are other solutions to this problem (Chef, Ansible), but if you'd like to
|
|
@@ -54,6 +54,7 @@ There are no configuration options (thank God!)
|
|
|
54
54
|
### How it works
|
|
55
55
|
|
|
56
56
|
`capistrano-safe-deploy-to` hooks to `before 'deploy:check'` task. It:
|
|
57
|
+
|
|
57
58
|
1. creates s `deploy_to` directory with `sudo mkdir -p <your_deploy_dir>`
|
|
58
59
|
2. gives proper ownership to deploy dir with
|
|
59
60
|
`sudo chown <deploy_user>:<deploy_user_group> <your_deploy_dir>`
|
|
@@ -61,6 +62,18 @@ There are no configuration options (thank God!)
|
|
|
61
62
|
It's simple, but you don't have to do or think about it. Let the computers
|
|
62
63
|
slave for you!
|
|
63
64
|
|
|
65
|
+
### More Capistrano automation?
|
|
66
|
+
|
|
67
|
+
If you'd like to streamline your Capistrano deploys, you might want to check
|
|
68
|
+
these zero-configuration, plug-n-play plugins:
|
|
69
|
+
|
|
70
|
+
- [capistrano-unicorn-nginx](https://github.com/bruno-/capistrano-unicorn-nginx)<br/>
|
|
71
|
+
no-configuration unicorn and nginx setup with sensible defaults
|
|
72
|
+
- [capistrano-postgresql](https://github.com/bruno-/capistrano-postgresql)<br/>
|
|
73
|
+
plugin that automates postgresql configuration and setup
|
|
74
|
+
- [capistrano-rbenv-install](https://github.com/bruno-/capistrano-rbenv-install)<br/>
|
|
75
|
+
would you like Capistrano to install rubies for you?
|
|
76
|
+
|
|
64
77
|
### License
|
|
65
78
|
|
|
66
79
|
[MIT](LICENSE.md)
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: capistrano-safe-deploy-to
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.
|
|
4
|
+
version: 1.1.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Bruno Sutic
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2014-
|
|
11
|
+
date: 2014-04-11 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: capistrano
|