Rebrand ServerMe → Deployzy + tokenless release CI/CD - #1
Merged
Conversation
- domain serverme.site → deployzy.com; brand + protocol headers (X-Deployzy-*) - npm: deployzy (CLI) + deployzy-sdk; pip: deployzy; repo → jams24/deployzy - OIDC release workflow: goreleaser + npm + PyPI on v* tags - CLI wrapper self-versions from package.json; installer retries + fixes - session features: referrals, webhooks, scoped API keys, multi-service, image/upload deploys - untrack build binary; ignore .claude/, build artifacts
jams24
added a commit
that referenced
this pull request
Aug 31, 2026
#1 Force sleep/wake (admin/ops, observe on demand): - engine.ForceSleep/ForceWake (platform-local only, bypass eligibility) - admin POST /projects/{id}/sleep|wake; 'Sleep' (moon) button on admin Projects rows, 'Wake' button on the Density 'Currently sleeping' list - verified live: force-sleep -> container exited/sleeping; request wakes + clears #2 Reclaim never-visited free apps (carefully): - eligibility now also includes free/local/non-admin apps with NULL last_request_at that were deployed >24h ago, flagged never_visited - the sweeper HTTP-probes those before sleeping: any HTTP response = real web server (safe to sleep, wakes on request); a connection error = worker/bot with no HTTP listener -> left running. This probe is the worker/bot protection. - audit-logged; per-project sleep_enabled=false still opts out Residual risk (documented): a background worker that ALSO exposes an HTTP health page would pass the probe and be slept, then not self-wake. Mitigated by 24h grace + opt-out; the zero-risk path is manual force-sleep (#1).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Full rebrand ServerMe → Deployzy plus a complete tokenless (OIDC) release pipeline.
X-Deployzy-*deployzy(CLI) +deployzy-sdk(JS SDK); pipdeployzy(Python SDK).github/workflows/release.yml): onv*tags → GitHub release binaries (goreleaser) + npm SDK + npm CLI + PyPI, all via OIDC trusted publishing (no stored tokens).claude/+ build artifactsdeployzyanddeployzy-sdk→ Settings → Trusted Publisher → GitHub Actions → repojams24/deployzy, workflowrelease.ymldeployzy→ Publishing → add GitHub publisher → ownerjams24, repodeployzy, workflowrelease.ymlRelease flow after merge
Bump versions in
sdk-js/package.json,npm-package/package.json,sdk-python/pyproject.toml→ commit →git tag vX.Y.Z && git push origin main --tags. Use v1.1.2+ (v1.1.0/1.1.1 already published; a v1.1.0 release already exists).