Support remote IRB
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Ruby
- Stars
- 478
- Forks
- 158
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 12
Description
(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
- Centralise IRB's IO interaction (#580)
- Enhance the IO layer with remote connecting medium options (TCP/IP, Socket...etc.)
- TBD
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100