fix: harden Multica self-hosted deployment and Gitea OAuth

Analysed against e3f1c5a62 files changedby 2233admin
Open PR on GitHub

Change-risk score

8.9out of 10Elevated
Repository health
2.9to2.9base against this head

This change sits in the top third of this repository's own risk distribution, the band worth reviewing closely.

The largest health movement is in multica_deploy.py, down 0.2. Nothing outside this PR depends on a contract it changed.

Files changed
2
in this diff
Contracts changed
0
removed or signature
Outside callers
0
not in this diff
Findings added
6
3 resolved

Blast radius on the repo map

Every file in the repository, grouped into its own directories and sized by lines. The ones this PR changes are lit, and everything that imports them is marked.

adapters/agent-plugin…design/changesdocsspec
changed, health fellchanged, health rosechanged, health heldimports a changed fileuntouchedchanged by this PR

Drawing 45 of 45 files at a readable size, grouped by directory and sized by lines of code. 2 changed here reach 1 more by import.

Changed

What this PR added, and what it took away

Introduced findings are the ones inside the lines this PR added, not the file's existing ones. The resolved column is the only place in the product that lists them.

Introduced (6)
  • mediumnested complexity
    multica_deploy.py:990

    copy_to_nas nests 4 levels deep

  • mediumnested complexity
    multica_deploy.py:373

    configure_desktop_lifecycle nests 4 levels deep

  • mediumlarge method
    multica_deploy.py:3187

    deploy is 96 lines long

  • mediumlarge method
    multica_deploy.py:3001

    doctor is 96 lines long

  • lowerror handling
    multica_deploy.py:1006

    broad `except Exception` catches unrelated errors and can hide bugs

  • lowlarge method
    multica_deploy.py:669

    sync_desktop is 65 lines long

Resolved (3)
  • bumpy road
    multica_deploy.py
  • io in loop
    multica_deploy.py
  • churn risk
    test_multica_deploy.py

Tests that cover this change

Test files that import a file this PR changes. Not a coverage measurement: it is the import graph, so it says which tests are worth running, not which lines they reach.

  • test_fleet_apply.py
  • test_fleet_plan.py

Get this on your own pull requests

This page came from an index of 2233admin/multica-deployment-tool. No model calls, no configuration, and it refreshes on every push. Install the bot and every pull request gets one of these.