capistrano-remote 0.2.1 → 0.3.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 +5 -5
- data/CHANGELOG.md +17 -1
- data/README.md +2 -0
- data/capistrano-remote.gemspec +5 -6
- data/lib/capistrano/remote.rb +1 -1
- data/lib/capistrano/remote/version.rb +1 -1
- data/lib/capistrano/tasks/remote.rake +3 -1
- metadata +7 -8
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
|
-
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: 28ce2ea5f7e8274ff708a6d3bd8023a17f120358627256d526a1f93280cc2f4b
|
4
|
+
data.tar.gz: d5211b1aac4872ed5cbf84156a5cae5d58d57a3a0a9841ef725974d019b754bc
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: dadee3efe24b7b51139f7b63026bd572ec0ea6a70d95d32583bf9d33c903c5c6c1307a18b1a1ae531419399091bafa6d7e9a81dff661e5e61883a7dd03b39c38
|
7
|
+
data.tar.gz: 30ec5fc312be24681d19bb57db2a55ab3e26db3bff317202cf5ea9375217e7ba8d735e70a495514556f983d717adc1f8513200b62f53a71662590681238a269b
|
data/CHANGELOG.md
CHANGED
@@ -5,7 +5,23 @@ This project adheres to [Semantic Versioning](http://semver.org/).
|
|
5
5
|
|
6
6
|
## Unreleased
|
7
7
|
|
8
|
-
|
8
|
+
### Added
|
9
|
+
|
10
|
+
-
|
11
|
+
|
12
|
+
### Fixed
|
13
|
+
|
14
|
+
-
|
15
|
+
|
16
|
+
### Changed
|
17
|
+
|
18
|
+
-
|
19
|
+
|
20
|
+
## [0.3.0] - 2019-09-25
|
21
|
+
|
22
|
+
### Added
|
23
|
+
|
24
|
+
- cap remote:console is now ready for Rails 6. (@ifsc01)
|
9
25
|
|
10
26
|
## [0.2.1] - 2018-02-13
|
11
27
|
|
data/README.md
CHANGED
@@ -1,5 +1,7 @@
|
|
1
1
|
# Capistrano Remote
|
2
2
|
|
3
|
+
[](https://codeclimate.com/github/substancelab/capistrano-remote/maintainability)
|
4
|
+
|
3
5
|
Every so often you need to look at your production data or otherwise run some manual maintenance tasks in your production Rails application.
|
4
6
|
|
5
7
|
Sure, you could SSH to the server, find the proper path, and remember the correct invocation for your rails console, but we already have an SSH automation tool; Capistrano.
|
data/capistrano-remote.gemspec
CHANGED
@@ -1,5 +1,4 @@
|
|
1
|
-
|
2
|
-
lib = File.expand_path('../lib', __FILE__)
|
1
|
+
lib = File.expand_path('lib', __dir__)
|
3
2
|
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
4
3
|
require 'capistrano/remote/version'
|
5
4
|
|
@@ -11,13 +10,13 @@ Gem::Specification.new do |spec|
|
|
11
10
|
|
12
11
|
spec.summary = \
|
13
12
|
'Capistrano tasks to start a Rails console or dbconsole on your servers'
|
14
|
-
spec.description = <<-
|
13
|
+
spec.description = <<-DESCRIPTION
|
15
14
|
Every so often you need to look at your production data or otherwise run
|
16
15
|
some manual maintenance tasks in your production Rails application.
|
17
16
|
|
18
17
|
This gem adds tasks to Capistrano that lets you start a Rails console or
|
19
18
|
dbconsole on your servers without manually SSH'ing.
|
20
|
-
|
19
|
+
DESCRIPTION
|
21
20
|
|
22
21
|
spec.homepage = 'https://github.com/substancelab/capistrano-remote'
|
23
22
|
spec.license = 'MIT'
|
@@ -31,6 +30,6 @@ Gem::Specification.new do |spec|
|
|
31
30
|
|
32
31
|
spec.add_dependency 'capistrano', '~> 3.0'
|
33
32
|
|
34
|
-
spec.add_development_dependency 'bundler', '~>
|
35
|
-
spec.add_development_dependency 'rake', '~>
|
33
|
+
spec.add_development_dependency 'bundler', '~> 2.0'
|
34
|
+
spec.add_development_dependency 'rake', '~> 12.3'
|
36
35
|
end
|
data/lib/capistrano/remote.rb
CHANGED
@@ -1,10 +1,11 @@
|
|
1
|
+
# rubocop:disable Metrics/BlockLength
|
1
2
|
namespace :remote do
|
2
3
|
desc 'Run and attach to a remote Rails console'
|
3
4
|
task :console do
|
4
5
|
rails_env = fetch(:rails_env)
|
5
6
|
on roles(:db) do |host|
|
6
7
|
Capistrano::Remote::Runner.new(host).rails(
|
7
|
-
"console #{rails_env}"
|
8
|
+
"console -e #{rails_env}"
|
8
9
|
)
|
9
10
|
end
|
10
11
|
end
|
@@ -30,3 +31,4 @@ namespace :remote do
|
|
30
31
|
end
|
31
32
|
end
|
32
33
|
end
|
34
|
+
# rubocop:enable Metrics/BlockLength
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: capistrano-remote
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.3.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Jakob Skjerning
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date:
|
11
|
+
date: 2019-09-25 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: capistrano
|
@@ -30,28 +30,28 @@ dependencies:
|
|
30
30
|
requirements:
|
31
31
|
- - "~>"
|
32
32
|
- !ruby/object:Gem::Version
|
33
|
-
version: '
|
33
|
+
version: '2.0'
|
34
34
|
type: :development
|
35
35
|
prerelease: false
|
36
36
|
version_requirements: !ruby/object:Gem::Requirement
|
37
37
|
requirements:
|
38
38
|
- - "~>"
|
39
39
|
- !ruby/object:Gem::Version
|
40
|
-
version: '
|
40
|
+
version: '2.0'
|
41
41
|
- !ruby/object:Gem::Dependency
|
42
42
|
name: rake
|
43
43
|
requirement: !ruby/object:Gem::Requirement
|
44
44
|
requirements:
|
45
45
|
- - "~>"
|
46
46
|
- !ruby/object:Gem::Version
|
47
|
-
version: '
|
47
|
+
version: '12.3'
|
48
48
|
type: :development
|
49
49
|
prerelease: false
|
50
50
|
version_requirements: !ruby/object:Gem::Requirement
|
51
51
|
requirements:
|
52
52
|
- - "~>"
|
53
53
|
- !ruby/object:Gem::Version
|
54
|
-
version: '
|
54
|
+
version: '12.3'
|
55
55
|
description: |2
|
56
56
|
Every so often you need to look at your production data or otherwise run
|
57
57
|
some manual maintenance tasks in your production Rails application.
|
@@ -97,8 +97,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
97
97
|
- !ruby/object:Gem::Version
|
98
98
|
version: '0'
|
99
99
|
requirements: []
|
100
|
-
|
101
|
-
rubygems_version: 2.6.12
|
100
|
+
rubygems_version: 3.0.6
|
102
101
|
signing_key:
|
103
102
|
specification_version: 4
|
104
103
|
summary: Capistrano tasks to start a Rails console or dbconsole on your servers
|