Repository navigation
Conversation
Loopable is becoming a desktop app, so the Worker now serves the front page and its legal pages and nothing else. The app's pages go to the front page, and sign-in and the runner API answer 410 with where Loopable went. Nothing reads the database. The cron that woke the dispatcher every minute is gone, and the container may sleep after ten idle minutes instead of renewing its own timer, so it stops costing. The front page says Loopable is coming to the Mac in place of signing in. The database, secrets and container definition are all kept, and docs/hosting.md says how to run the service again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
What
Loopable is becoming a desktop app, so this pauses the hosted service on Cloudflare and keeps only loop.goodone.si's front page running.
LOOPABLE_SITE_ONLY=1, it serves/,/privacyand/terms. The app's pages redirect to/./api/*, including sign-in and the runner API, answers 410 with a message saying where Loopable went. No request reads the database or wakes the dispatcher.Kept
The Turso database and its data, the Worker's secrets, the container definition (removing it would need a migration that deletes its storage), and the deploy workflow.
docs/hosting.mdsays how to turn the service back on.Verified
The built Worker ran locally under
wrangler devwith no database credentials:/,/privacy,/terms/inbox,/loops/abc//api/runners/claim,/api/auth/signin/favicon.svgThe front page shows "Coming to the Mac" and no sign-in. Typecheck and all tests pass.
After merging
Merging deploys. Then check in the Cloudflare dashboard that the dispatcher container has stopped, about ten minutes after the deploy.
🤖 Generated with Claude Code