Move ipx into its own Arcane project, with a sample compose for others #208
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ipx runs as one service in the Arcane project
content, beside audiobookshelf, immich, Plex and others. Give it its own project,ipx(/mnt/fast/arcane/projects/ipx), where the containers of the split (#207) will join it. The repo's docker-compose.yml becomes a sample showing how to set ipx up, not a copy of production's file.Moving changes ipx's network, and the Cloudflare Access trust is tied to that network's gateway (192.168.16.1, content_default). The new project pins its subnet so the gateway is known, and config.toml's trusted_proxies follows it.
Done in
c2cea0f. Production runs from /mnt/fast/arcane/projects/ipx/compose.yaml (ipx.env beside it), on ipx_default pinned to 192.168.64.0/20; trusted_proxies is 192.168.64.1, checked with a forged Access token from a Docker bridge, which reached the token check. ipx is gone from content's compose file; backups of both edited files are beside them as *.bak-pre-ipx-project-20261012. Postgres stays on the databases project's server. The repo's docker-compose.yml is now a sample: ipx alone on SQLite. The ipx-prod-check skill finds ipx by container name, which did not change, so it needed nothing.