Compare commits

..

No commits in common. "main" and "v1.1.0" have entirely different histories.
main ... v1.1.0

View File

@ -7,11 +7,6 @@ project never looks idle. One workflow file, plain bash and curl, nothing to ins
If your project is already paused, [restore it first](#how-to-restore-a-paused-project); a
workflow cannot unpause it.
Want the workflow with a copy button, no `git clone`? It's live at
[scribase.com/supabase-keep-alive](https://scribase.com/supabase-keep-alive?utm_source=rithub&utm_medium=readme&utm_campaign=supabase-keep-alive)
(raw file: [scribase.com/supabase-keep-alive.yml](https://scribase.com/supabase-keep-alive.yml)).
Move off Supabase free-tier pauses entirely: [Scribase](https://scribase.com/supabase-keep-alive?utm_source=rithub&utm_medium=readme&utm_campaign=supabase-keep-alive) — Postgres that scales to zero and wakes on request instead of pausing, first project free forever.
| You want | Use | Needs |
|---|---|---|
| The fastest fix | [The workflow below](#set-it-up-in-three-steps) | A GitHub repository |
@ -357,7 +352,7 @@ without CORS headers, so your app reports "Failed to fetch" or "Load failed" ins
## If you would rather not babysit it
A keep-alive exists because a free project nobody touches for a week is turned off and has to be
turned back on by hand. [Scribase](https://scribase.com/supabase-keep-alive?utm_source=rithub&utm_medium=readme&utm_campaign=supabase-keep-alive) is a backend built around the opposite behaviour: each
turned back on by hand. [Scribase](https://scribase.com/?utm_source=rithub&utm_medium=readme&utm_campaign=supabase-keep-alive) is a backend built around the opposite behaviour: each
project is Postgres, Auth, Storage and Realtime, and an idle project scales to zero on its own and
wakes on the next request. There is nothing to keep alive and nothing to restore.