feat: publish circuitforge-core to Forgejo Packages (private PyPI) to simplify install #23

Open
opened 2026-04-05 22:09:03 -07:00 by pyr0ball · 0 comments
Owner

Problem

The self-hosted installer must clone circuitforge-core separately as a sibling repo because it is not on any package registry. This means:

  • The private repo requires auth credentials during install
  • The compose.yml build context (context: ..) is non-obvious to users
  • install.sh cannot be a true one-liner (needs token or SSH key for the private clone)

Proposed

Publish circuitforge-core to Forgejo Packages as a private PyPI index. Then:

pip install --extra-index-url https://git.opensourcesolarpunk.com/api/packages/Circuit-Forge/pypi/simple/ circuitforge-core

The Dockerfile and install.sh become simpler, and external self-hosters no longer need repo access to circuitforge-core.

Alternative

Make circuitforge-core MIT and publish to public PyPI. Keeps the MIT code open (it is already MIT-licensed), simplifies install for everyone.

Refs

  • cf-core milestone: circuitforge-core next milestone (product #3)
  • Raised during self-hosted install testing on Strahl
## Problem The self-hosted installer must clone `circuitforge-core` separately as a sibling repo because it is not on any package registry. This means: - The private repo requires auth credentials during install - The `compose.yml` build context (`context: ..`) is non-obvious to users - `install.sh` cannot be a true one-liner (needs token or SSH key for the private clone) ## Proposed Publish `circuitforge-core` to Forgejo Packages as a private PyPI index. Then: ``` pip install --extra-index-url https://git.opensourcesolarpunk.com/api/packages/Circuit-Forge/pypi/simple/ circuitforge-core ``` The Dockerfile and `install.sh` become simpler, and external self-hosters no longer need repo access to `circuitforge-core`. ## Alternative Make `circuitforge-core` MIT and publish to public PyPI. Keeps the MIT code open (it is already MIT-licensed), simplifies install for everyone. ## Refs - cf-core milestone: circuitforge-core next milestone (product #3) - Raised during self-hosted install testing on Strahl
pyr0ball added this to the Public Launch milestone 2026-04-05 22:09:03 -07:00
pyr0ball added the
backlog
infra
labels 2026-04-05 22:09:03 -07:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/snipe#23
No description provided.