Circuit-Forge/pagepiper
3
0
Fork 0
Code Issues 3 Pull requests Projects Releases 1 Packages Wiki Activity Actions

feat: rename CF_ORCH_URL → GPU_SERVER_URL for local-first clarity #10

New issue
Open
opened 2026-05-17 09:50:12 -07:00 by pyr0ball · 0 comments
pyr0ball commented 2026-05-17 09:50:12 -07:00
Owner
Copy link

Summary

The CF_ORCH_URL environment variable name makes sense in a cloud/orch context but is confusing for local-first users. Kiwi has already implemented this pattern.

Pattern (from Kiwi)

  • Primary env var: GPU_SERVER_URL — user-visible name that maps to what it actually does for self-hosters
  • Backward compat: CF_ORCH_URL still accepted (secondary fallback)
  • At startup, resolve GPU_SERVER_URL || CF_ORCH_URL and normalize into a single internal value
  • For Paid+ tiers: default GPU_SERVER_URL to the cf-orch coordinator URL via license check (so cloud users don't need to configure it)

Acceptance Criteria

  • Config reads GPU_SERVER_URL first, falls back to CF_ORCH_URL
  • README and .env.example updated to document GPU_SERVER_URL
  • Paid+ tier default wired through license/tier check
  • Existing CF_ORCH_URL deployments continue to work unchanged

Reference

Kiwi implementation: app/core/config.py — GPU_SERVER_URL field with CF_ORCH_URL fallback + startup normalization hook

## Summary The `CF_ORCH_URL` environment variable name makes sense in a cloud/orch context but is confusing for local-first users. Kiwi has already implemented this pattern. ## Pattern (from Kiwi) - Primary env var: `GPU_SERVER_URL` — user-visible name that maps to what it actually does for self-hosters - Backward compat: `CF_ORCH_URL` still accepted (secondary fallback) - At startup, resolve `GPU_SERVER_URL || CF_ORCH_URL` and normalize into a single internal value - For Paid+ tiers: default `GPU_SERVER_URL` to the cf-orch coordinator URL via license check (so cloud users don't need to configure it) ## Acceptance Criteria - [ ] Config reads `GPU_SERVER_URL` first, falls back to `CF_ORCH_URL` - [ ] README and .env.example updated to document `GPU_SERVER_URL` - [ ] Paid+ tier default wired through license/tier check - [ ] Existing `CF_ORCH_URL` deployments continue to work unchanged ## Reference Kiwi implementation: `app/core/config.py` — `GPU_SERVER_URL` field with `CF_ORCH_URL` fallback + startup normalization hook
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/pagepiper#10
No description provided.
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?