Split ipx into directory, backend and frontend #207
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?
Split ipx into three pieces in this repo, each its own image and deploy:
ipx-directoryat https://ipx-dir.sdf1.net, a shared catalogue of public podcasts, metadata only. Access by tokens in its config file, eachro,rworrwa, revoked one at a time.ipx, everything else: accounts, subscriptions, scans, downloads, playback, the API.ipx-web, the page as static files behind Caddy, which proxies the API on the same origin.Why: deploy each on its own, a clean API for other clients, a scan or download never touching the page or the directory, and smaller pieces than today's 3,000-line files.
Phases, each deployable:
rwatokens; mockups first)Risk carried throughout: the directory stores feed URLs, and a URL can hold a subscriber's key.
looks_private()runs before a snapshot is sent and again when it arrives, a per-feed unlisted flag covers what it misses, and anrwatoken can remove and block a feed.Wording: the per-feed flag is private (#205). A private feed is never sent to the directory.
Split status: #202 workspace, #204 directory, #205 ipx uses it, #203 page in ipx-web, #208 own Arcane project: all done and deployed. Left: #206, directory admin from ipx, mockups first.
Done: the split is in production as three services in the Arcane project ipx, each with its own version, changelog and traces: ipx-web (#203, #210, #213), ipx (#202, #205, #211), ipx-directory (#204, #206, #213), with the move to its own project (#208).