Support remote IRB

Open
#672 0 comments 7 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
cli

Research direction

Start by reviewing the IRB IO interaction and the centralisation proposed in #580, along with the related debugging enhancements in #575. Investigate how a remote connection medium such as TCP/IP or Socket could replace direct standard IO, and define completion as usable remote IRB access for tools such as foreman.

Written by the indexing model from the issue text.

Description

enhancement

(originally proposed by @zzak)

Description

Currently IRB can't be used without direct access to standard IO. This makes it hard to use with tools like foreman.

If we expect IRB to become a more powerful debugging tool, especially after #575 and similar enhancements, the need to connect to it remotely will only grow.

Implementation

  1. Centralise IRB's IO interaction (#580)
  2. Enhance the IO layer with remote connecting medium options (TCP/IP, Socket...etc.)
  3. TBD
Dominant language
Ruby
Stars
477
Forks
165
Avg merge
1d 19h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/irb

All issues in ruby/irb

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.