docs: note media-core Arcane onboarding state
This commit is contained in:
@@ -1,6 +1,7 @@
|
|||||||
# media-core
|
# media-core
|
||||||
|
|
||||||
Arcane-managed media automation services on `media-core` (`192.168.50.46`).
|
Media automation services on `media-core` (`192.168.50.46`), with the Compose
|
||||||
|
source prepared for Arcane management.
|
||||||
|
|
||||||
This first migration group contains NZBHydra2, Lidarr, and Whisparr. Download
|
This first migration group contains NZBHydra2, Lidarr, and Whisparr. Download
|
||||||
clients remain on unRaid; Lidarr and Whisparr use the unRaid SABnzbd instance.
|
clients remain on unRaid; Lidarr and Whisparr use the unRaid SABnzbd instance.
|
||||||
@@ -14,3 +15,9 @@ Host prerequisites:
|
|||||||
|
|
||||||
The image digests match the source containers on `192.168.50.10` at the
|
The image digests match the source containers on `192.168.50.10` at the
|
||||||
2026-09-05 migration snapshot. Upgrade only after migration acceptance.
|
2026-09-05 migration snapshot. Upgrade only after migration acceptance.
|
||||||
|
|
||||||
|
The initial cutover was deployed from `/opt/media-core/compose.yaml`. Arcane
|
||||||
|
currently sees the containers but does not yet hold a Project record. A first
|
||||||
|
Git Sync registration was rolled back because Arcane v2.9.0 incorrectly bound
|
||||||
|
it to Environment `0` and the Manager-side repository clone timed out. Do not
|
||||||
|
assume Git pushes redeploy this stack until that control-plane issue is fixed.
|
||||||
|
|||||||
Reference in New Issue
Block a user