pry-janitor 0.1.4

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: 32ce27be1a29f991cf6bb348c2103211549396fe4617efbe452f784324ec88e5
4
+ data.tar.gz: 1227aa2510a61987878ca399be09ebe6a7f3ff2e41e1107a1cd7f392f445f2a5
5
+ SHA512:
6
+ metadata.gz: 2f2c0aa2d7088a01af5ca24ab4727cd67f35bc92da04f4dc861d25e62cc3aa994ffa707aec6ee8e186d9c92c4a17c1451cf50b18e862faf7a5e5a601317e3ea9
7
+ data.tar.gz: c5983ff8c34ae7630b2d87daec756d31544e11e62bbf98b6cd1cafa8636d4e2f45f973229736132aad322ed27d147bd982666c427f155b677fbbb09bec07b31d
@@ -0,0 +1,9 @@
1
+ /.bundle/
2
+ /.yardoc
3
+ /_yardoc/
4
+ /coverage/
5
+ /doc/
6
+ /pkg/
7
+ /spec/reports/
8
+ /tmp/
9
+ *.gem
@@ -0,0 +1,74 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ nationality, personal appearance, race, religion, or sexual identity and
10
+ orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at tony@angel.co. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at [http://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: http://contributor-covenant.org
74
+ [version]: http://contributor-covenant.org/version/1/4/
data/Gemfile ADDED
@@ -0,0 +1,4 @@
1
+ source "https://rubygems.org"
2
+
3
+ # Specify your gem's dependencies in pry-janitor.gemspec
4
+ gemspec
@@ -0,0 +1,26 @@
1
+ PATH
2
+ remote: .
3
+ specs:
4
+ pry-janitor (0.1.4)
5
+ pry (~> 0.11)
6
+
7
+ GEM
8
+ remote: https://rubygems.org/
9
+ specs:
10
+ coderay (1.1.2)
11
+ method_source (0.9.2)
12
+ pry (0.12.2)
13
+ coderay (~> 1.1.0)
14
+ method_source (~> 0.9.0)
15
+ rake (10.5.0)
16
+
17
+ PLATFORMS
18
+ ruby
19
+
20
+ DEPENDENCIES
21
+ bundler (~> 2.0)
22
+ pry-janitor!
23
+ rake (~> 10.0)
24
+
25
+ BUNDLED WITH
26
+ 2.0.1
@@ -0,0 +1,21 @@
1
+ The MIT License (MIT)
2
+
3
+ Copyright (c) 2019 Tony
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in
13
+ all copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
21
+ THE SOFTWARE.
@@ -0,0 +1,48 @@
1
+ # pry-janitor
2
+
3
+ :knife: Kill idle `pry` sessions
4
+
5
+ ## Installation
6
+
7
+ Add this line to your application's Gemfile:
8
+
9
+ ```ruby
10
+ gem 'pry-janitor'
11
+ ```
12
+
13
+ And then execute:
14
+
15
+ $ bundle
16
+
17
+ Or install it yourself as:
18
+
19
+ $ gem install pry-janitor
20
+
21
+ ## Usage
22
+
23
+ Production rails consoles will automatically exit after 2 hours of inactivity.
24
+
25
+ To configure the gem for other consoles or to re-configure the gem for production rails consoles run:
26
+
27
+ ```ruby
28
+ # kill pry session after one hour
29
+ PryJanitor.auto_exit_after(60 * 60)
30
+ ```
31
+
32
+ ## Development
33
+
34
+ After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
35
+
36
+ To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
37
+
38
+ ## Contributing
39
+
40
+ Bug reports and pull requests are welcome on GitHub at https://github.com/venturehacks/pry-janitor. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
41
+
42
+ ## License
43
+
44
+ The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
45
+
46
+ ## Code of Conduct
47
+
48
+ Everyone interacting in the pry-janitor project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/pry-janitor/blob/master/CODE_OF_CONDUCT.md).
@@ -0,0 +1,2 @@
1
+ require "bundler/gem_tasks"
2
+ task :default => :spec
@@ -0,0 +1,10 @@
1
+ #!/usr/bin/env ruby
2
+
3
+ require 'bundler/setup'
4
+ require 'pry-janitor'
5
+
6
+ # You can add fixtures and/or initialization code here to make experimenting
7
+ # with your gem easier. You can also use a different console, if you like.
8
+
9
+ require 'pry'
10
+ Pry.start
@@ -0,0 +1,8 @@
1
+ #!/usr/bin/env bash
2
+ set -euo pipefail
3
+ IFS=$'\n\t'
4
+ set -vx
5
+
6
+ bundle install
7
+
8
+ # Do any other automated setup that you need to do here
@@ -0,0 +1,102 @@
1
+ require 'pry-janitor/version'
2
+ require 'singleton'
3
+ require 'pry'
4
+
5
+ class PryJanitor
6
+ include Singleton
7
+
8
+ CHECK_ACTIVITY_SECONDS = 60
9
+ DEFAULT_TIMEOUT_SECONDS = 60 * 60 * 2
10
+ PRY_HOOK_NAME = :pry_janitor
11
+
12
+ ACTIVITY_SIGNAL = 'USR1'.freeze
13
+ PAUSE_SIGNAL = 'USR2'.freeze
14
+ KILL_SIGNAL = 'TERM'.freeze
15
+ EXIT_SIGNAL = 'EXIT'.freeze
16
+
17
+ def self.auto_exit_after(timeout = DEFAULT_TIMEOUT_SECONDS)
18
+ instance.auto_exit_after(timeout)
19
+ end
20
+
21
+ def self.register_pry_hooks
22
+ instance.register_pry_hooks
23
+ end
24
+
25
+ def auto_exit_after(timeout)
26
+ kill_child
27
+ with_install_handlers do
28
+ @parent_pid = Process.pid
29
+ @child_pid = Process.fork { child_process(timeout) }
30
+ end
31
+ kill_child_on_exit
32
+ end
33
+
34
+ def register_pry_hooks
35
+ # pause last activity for long running commands
36
+ Pry.hooks.add_hook(:before_eval, PRY_HOOK_NAME) do
37
+ signal_child(PAUSE_SIGNAL)
38
+ end
39
+
40
+ # record activity when a command finishes, line is read, or session starts
41
+ Pry.hooks.add_hook(:after_eval, PRY_HOOK_NAME) do
42
+ signal_child(ACTIVITY_SIGNAL)
43
+ end
44
+
45
+ Pry.hooks.add_hook(:after_read, PRY_HOOK_NAME) do
46
+ signal_child(ACTIVITY_SIGNAL)
47
+ end
48
+
49
+ Pry.hooks.add_hook(:before_session, PRY_HOOK_NAME) do
50
+ signal_child(ACTIVITY_SIGNAL)
51
+ end
52
+ end
53
+
54
+ private
55
+
56
+ # 1. install signal handlers in the parent so the child is immediately ready
57
+ # 2. re-install pre-existing signal handlers back into the parent
58
+ def with_install_handlers
59
+ prev_sig1 = Signal.trap(ACTIVITY_SIGNAL) { @last_activity = Time.now }
60
+ prev_sig2 = Signal.trap(PAUSE_SIGNAL) { @last_activity = nil }
61
+ yield
62
+ Signal.trap(ACTIVITY_SIGNAL, prev_sig1)
63
+ Signal.trap(PAUSE_SIGNAL, prev_sig2)
64
+ end
65
+
66
+ def child_process(timeout)
67
+ loop do
68
+ begin
69
+ # kill parent and exit loop if last activity is longer than timeout
70
+ if @last_activity && @last_activity < Time.now - timeout
71
+ Process.kill(KILL_SIGNAL, @parent_pid)
72
+ end
73
+ sleep CHECK_ACTIVITY_SECONDS
74
+ rescue Interrupt
75
+ # parent exited, exit loop
76
+ break
77
+ end
78
+ end
79
+ end
80
+
81
+ def signal_child(signal)
82
+ Process.kill(signal, @child_pid) if @child_pid
83
+ end
84
+
85
+ def kill_child
86
+ signal_child(KILL_SIGNAL)
87
+ end
88
+
89
+ def kill_child_on_exit
90
+ Signal.trap(EXIT_SIGNAL) { kill_child }
91
+ end
92
+ end
93
+
94
+ # need to register the hooks before pry starts
95
+ PryJanitor.register_pry_hooks
96
+
97
+ # auto exit if production rails console
98
+ if defined?(Rails)
99
+ prod = Rails.env.production?
100
+ console = Rails.const_defined?('Console')
101
+ PryJanitor.auto_exit_after if prod && console
102
+ end
@@ -0,0 +1,3 @@
1
+ class PryJanitor
2
+ VERSION = '0.1.4'.freeze
3
+ end
@@ -0,0 +1,29 @@
1
+ lib = File.expand_path('lib', __dir__)
2
+ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
3
+ require 'pry-janitor/version'
4
+
5
+ Gem::Specification.new do |spec|
6
+ spec.name = 'pry-janitor'
7
+ spec.version = PryJanitor::VERSION
8
+ spec.authors = ['Tony']
9
+ spec.email = ['tony@angel.co']
10
+
11
+ spec.summary = '🔪 Kill idle pry sessions'
12
+ spec.description = 'Production rails consoles will automatically exit after 2 hours of inactivity.'
13
+ spec.homepage = 'https://github.com/venturehacks/pry-janitor'
14
+ spec.license = 'MIT'
15
+
16
+ # Specify which files should be added to the gem when it is released.
17
+ # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
18
+ spec.files = Dir.chdir(File.expand_path(__dir__)) do
19
+ `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
20
+ end
21
+ spec.bindir = 'exe'
22
+ spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
23
+ spec.require_paths = ['lib']
24
+
25
+ spec.add_dependency 'pry', '~> 0.11'
26
+
27
+ spec.add_development_dependency 'bundler', '~> 2.0'
28
+ spec.add_development_dependency 'rake', '~> 10.0'
29
+ end
metadata ADDED
@@ -0,0 +1,97 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: pry-janitor
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.1.4
5
+ platform: ruby
6
+ authors:
7
+ - Tony
8
+ autorequire:
9
+ bindir: exe
10
+ cert_chain: []
11
+ date: 2019-04-30 00:00:00.000000000 Z
12
+ dependencies:
13
+ - !ruby/object:Gem::Dependency
14
+ name: pry
15
+ requirement: !ruby/object:Gem::Requirement
16
+ requirements:
17
+ - - "~>"
18
+ - !ruby/object:Gem::Version
19
+ version: '0.11'
20
+ type: :runtime
21
+ prerelease: false
22
+ version_requirements: !ruby/object:Gem::Requirement
23
+ requirements:
24
+ - - "~>"
25
+ - !ruby/object:Gem::Version
26
+ version: '0.11'
27
+ - !ruby/object:Gem::Dependency
28
+ name: bundler
29
+ requirement: !ruby/object:Gem::Requirement
30
+ requirements:
31
+ - - "~>"
32
+ - !ruby/object:Gem::Version
33
+ version: '2.0'
34
+ type: :development
35
+ prerelease: false
36
+ version_requirements: !ruby/object:Gem::Requirement
37
+ requirements:
38
+ - - "~>"
39
+ - !ruby/object:Gem::Version
40
+ version: '2.0'
41
+ - !ruby/object:Gem::Dependency
42
+ name: rake
43
+ requirement: !ruby/object:Gem::Requirement
44
+ requirements:
45
+ - - "~>"
46
+ - !ruby/object:Gem::Version
47
+ version: '10.0'
48
+ type: :development
49
+ prerelease: false
50
+ version_requirements: !ruby/object:Gem::Requirement
51
+ requirements:
52
+ - - "~>"
53
+ - !ruby/object:Gem::Version
54
+ version: '10.0'
55
+ description: Production rails consoles will automatically exit after 2 hours of inactivity.
56
+ email:
57
+ - tony@angel.co
58
+ executables: []
59
+ extensions: []
60
+ extra_rdoc_files: []
61
+ files:
62
+ - ".gitignore"
63
+ - CODE_OF_CONDUCT.md
64
+ - Gemfile
65
+ - Gemfile.lock
66
+ - LICENSE.txt
67
+ - README.md
68
+ - Rakefile
69
+ - bin/console
70
+ - bin/setup
71
+ - lib/pry-janitor.rb
72
+ - lib/pry-janitor/version.rb
73
+ - pry-janitor.gemspec
74
+ homepage: https://github.com/venturehacks/pry-janitor
75
+ licenses:
76
+ - MIT
77
+ metadata: {}
78
+ post_install_message:
79
+ rdoc_options: []
80
+ require_paths:
81
+ - lib
82
+ required_ruby_version: !ruby/object:Gem::Requirement
83
+ requirements:
84
+ - - ">="
85
+ - !ruby/object:Gem::Version
86
+ version: '0'
87
+ required_rubygems_version: !ruby/object:Gem::Requirement
88
+ requirements:
89
+ - - ">="
90
+ - !ruby/object:Gem::Version
91
+ version: '0'
92
+ requirements: []
93
+ rubygems_version: 3.0.3
94
+ signing_key:
95
+ specification_version: 4
96
+ summary: "\U0001F52A Kill idle pry sessions"
97
+ test_files: []