panter-rails-deploy 1.0.0 → 1.0.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Gemfile.lock +1 -3
- data/README.md +22 -0
- data/lib/panter-rails-deploy.rb +6 -1
- data/panter-rails-deploy.gemspec +1 -2
- metadata +1 -15
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: d0dac107926a516fd8f8b9314f23bbcf317c8559
|
4
|
+
data.tar.gz: 0206f92b8e94d26d0d42b973376150864182cee3
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 1f258ae3370c462786041f9501ce6077d6fe57483ce33b7f35476278844108367fd3b99781173ff12385e9aba9d7434953480378b75b80d11bc28cb735f7df5a
|
7
|
+
data.tar.gz: 4332616593d3b37a364b1eac5074cb61d4aaacac82a288ffdc351fd8d26692cb3cea5f7084affc953aadb1a1fa16f97cc2b6860b69cd0582ced25f2f931db5c7
|
data/Gemfile.lock
CHANGED
@@ -1,14 +1,13 @@
|
|
1
1
|
PATH
|
2
2
|
remote: .
|
3
3
|
specs:
|
4
|
-
panter-rails-deploy (1.0.
|
4
|
+
panter-rails-deploy (1.0.1)
|
5
5
|
capistrano
|
6
6
|
capistrano-bundler
|
7
7
|
capistrano-rails
|
8
8
|
capistrano-rbenv
|
9
9
|
capistrano-rbenv-install
|
10
10
|
dotenv-rails
|
11
|
-
execjs
|
12
11
|
therubyracer
|
13
12
|
unicorn-rails
|
14
13
|
|
@@ -35,7 +34,6 @@ GEM
|
|
35
34
|
dotenv (2.0.1)
|
36
35
|
dotenv-rails (2.0.1)
|
37
36
|
dotenv (= 2.0.1)
|
38
|
-
execjs (2.5.2)
|
39
37
|
i18n (0.7.0)
|
40
38
|
kgio (2.9.3)
|
41
39
|
libv8 (3.16.14.7)
|
data/README.md
CHANGED
@@ -34,3 +34,25 @@ This gem sets up everything you need to deploy your application on the Panter ra
|
|
34
34
|
```sh
|
35
35
|
cap production deploy
|
36
36
|
```
|
37
|
+
|
38
|
+
## dotenv setup
|
39
|
+
|
40
|
+
This is optional, but recommended:
|
41
|
+
|
42
|
+
- Add a file on your servers in `/home/app/app/shared/.env` with your keys:
|
43
|
+
```sh
|
44
|
+
RAILS_SECRET_KEY_BASE: ...
|
45
|
+
```
|
46
|
+
|
47
|
+
- If you need keys in development as well, add `.env` locally and add it to `.gitignore`
|
48
|
+
|
49
|
+
- Replace your keys in `config/secrets.yml` and other places with references to `ENV`:
|
50
|
+
```ruby
|
51
|
+
production:
|
52
|
+
secret_key_base: <%= ENV["RAILS_SECRET_KEY_BASE"] %>
|
53
|
+
```
|
54
|
+
|
55
|
+
- Update `config/deploy.rb` to symlink the `.env` file during deploy:
|
56
|
+
```ruby
|
57
|
+
set :linked_files, fetch(:linked_files, []).push('.env')
|
58
|
+
```
|
data/lib/panter-rails-deploy.rb
CHANGED
data/panter-rails-deploy.gemspec
CHANGED
@@ -1,6 +1,6 @@
|
|
1
1
|
Gem::Specification.new do |gem|
|
2
2
|
gem.name = 'panter-rails-deploy'
|
3
|
-
gem.version = '1.0.
|
3
|
+
gem.version = '1.0.1'
|
4
4
|
gem.date = '2015-06-01'
|
5
5
|
gem.summary = 'Capistrano setup for Panter Rails Hosting'
|
6
6
|
gem.authors = [ 'Markus Koller', 'Beat Seeliger' ]
|
@@ -22,6 +22,5 @@ Gem::Specification.new do |gem|
|
|
22
22
|
gem.add_dependency 'dotenv-rails'
|
23
23
|
|
24
24
|
# Asset pipeline dependencies
|
25
|
-
gem.add_dependency 'execjs'
|
26
25
|
gem.add_dependency 'therubyracer'
|
27
26
|
end
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: panter-rails-deploy
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.0.
|
4
|
+
version: 1.0.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Markus Koller
|
@@ -109,20 +109,6 @@ dependencies:
|
|
109
109
|
- - ">="
|
110
110
|
- !ruby/object:Gem::Version
|
111
111
|
version: '0'
|
112
|
-
- !ruby/object:Gem::Dependency
|
113
|
-
name: execjs
|
114
|
-
requirement: !ruby/object:Gem::Requirement
|
115
|
-
requirements:
|
116
|
-
- - ">="
|
117
|
-
- !ruby/object:Gem::Version
|
118
|
-
version: '0'
|
119
|
-
type: :runtime
|
120
|
-
prerelease: false
|
121
|
-
version_requirements: !ruby/object:Gem::Requirement
|
122
|
-
requirements:
|
123
|
-
- - ">="
|
124
|
-
- !ruby/object:Gem::Version
|
125
|
-
version: '0'
|
126
112
|
- !ruby/object:Gem::Dependency
|
127
113
|
name: therubyracer
|
128
114
|
requirement: !ruby/object:Gem::Requirement
|