Hosted deployment: flip the self-hosted default to split (phase 2)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 22/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker, docker-compose
- Domain
- devops, documentation
Research direction
Start from the compose files and the image entry where RUNNER_MODE gets its default, and read the compose equality tests (T03) that check them. The work is blocked until issues ##334 and ##332 land and a soak period has passed, so confirm those first. Done means the default is split, legacy still works via RUNNER_MODE=legacy, the docs and release notes cover the flip, the fallback and the App-then-runners deploy order, and the smoke and unit tests T01 to T04 pass.
Written by the indexing model from the issue text.
Description
Part of ##316. Phase 2.
Problem
After a soak period the split should become the default for self-hosted deployments, with the legacy mode kept as a documented fallback.
Design
Flip the default of RUNNER_MODE to split in the compose files and the image entry after a few weeks of operators running split without problems (the soak report is part of the PR). Update docs and release notes, keep legacy selectable, and add the deploy-order note (App first, then runners).
Scope
Default change, docs, release notes, deploy-order note.
Out of scope
Removing the legacy loop (##336).
Depends on
##334, ##332 and the soak period.
Test cases
| ID | kind | level | case | expected |
|---|---|---|---|---|
| T01 | regression | image smoke | stack smoke with defaults | jobs run through the split |
| T02 | regression | image smoke | RUNNER_MODE=legacy |
jobs run through the legacy loop |
| T03 | regression | unit | compose equality tests | pass |
| T04 | docs | review | release notes | state the flip, the fallback and the order |
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 17m
- Merged PRs (30d)
- 246
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from ExpidetGames/code-reviewer
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ExpidetGames/code-reviewer#464 ·
Maintainers usually reply within 1 day
-
area: app type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ExpidetGames/code-reviewer#308 ·
Maintainers usually reply within 1 day
-
type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ExpidetGames/code-reviewer#94 ·
Maintainers usually reply within 1 day
-
area: runner type: bug
Difficulty 3/5 1-2 days Newbie friendliness 64/100
ExpidetGames/code-reviewer#483 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 49/100
ExpidetGames/code-reviewer#479 ·
Maintainers usually reply within 1 day
All issues in ExpidetGames/code-reviewer
Similar issues
-
bug priority: P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug customer-reported data-plane question Service Attention Storage
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Azure/azure-rest-api-specs#47397 · 2 comments ·
Maintainers usually reply within 1 day
-
Claude thinking budget can shrink capped Haiku responses to 2,048 tokensPossibly taken @DavyMassoneto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
diegosouzapw/OmniRoute#17109 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
paperclipai/paperclip#16785 ·
Maintainers usually reply within 1 day