RexOps / RexOps/Rex

Rex-Server (Rex-Overlord)

Open
#676 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
Perl
Stars
737
Forks
214
PR merge metrics
No merged PRs in 30d

Description

We moved the ticket text to the wiki: https://github.com/RexOps/Rex/wiki/Rex-Server-&-Agent-(Overlord-&-Drone)

Feel free to discuess it here.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the Rex-Server (Rex-Overlord) specification in the linked Rex wiki page, since the issue says the ticket text was moved there. Review the discussion on this issue and the wiki requirements first; the issue itself does not define a concrete implementation target or what completion looks like.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.