Repair, update or remove an app's setup
Keep Cockpitify's ops layer in your Supabase project up to date from Connections, repair a broken setup without losing data, or remove it completely.
Each connected app has an ops layer in its Supabase project. You can update it to the latest version, repair it, or remove it completely. Updates and repairs start from App → Connections, on the Supabase project row.
Check the project
Open App → Connections. The Supabase project row shows the ops version and a state:
| State | What it means |
|---|---|
| Working | Everything answers |
| Needs update | An update brings something new or a security fix |
| Broken part | A part is missing, a scheduled step failed, or the project doesn’t answer (it may be paused) |
| Waiting for data | Setup is running |
| Not set up | No project is connected |
Tap the row for the project’s details: the next step, problems, missing parts and Open in Supabase dashboard. See Connections for the other rows.
The update mark
When a new version is out, a small mark shows beside the row’s title. Its colour says how much the update matters:
- Grey: fixes only. Nothing breaks without it; update when it suits you.
- Purple: it brings something new or a security fix. The row says Needs update.
- Orange: this install is too old to use safely. Update it now.
Hover over the mark on the web, or tap it on the phone, to see what the update brings. Other rows that need a newer project show the same mark with “Comes with the project update”. On the phone, a strip under the header also names an update worth having.
Update
Only the owner and admins can update.
- In App → Connections, tap the mark, then Update. On the web, open the Supabase project row and tap Update to the new version; What’s new lists the changes.
- Choose how to apply it: Automatic or Do it myself (below).
- For Automatic, approve Cockpitify in Supabase in the browser, review the changes, and tap Confirm and update.
- Wait for is up to date. It takes about a minute, and you can leave the screen.
Every update and repair asks for Supabase approval again, because the access key is deleted after each run.
Do it myself
If you’d rather not give Cockpitify access to your project, choose Do it myself. You run the update with your own Supabase login, and Cockpitify only checks the result.
- Review what changes. Nothing is deleted, and none of your own tables are read or changed.
- Run the SQL in the SQL Editor. Copy or download it, paste it into a new query and press Run.
- Deploy the functions with the Supabase CLI. The source files (.zip) download from the web console on a computer.
- Check it. Tap I’ve run it — check. Cockpitify asks your project’s ops-api for its version and health.
Repair
Repair reinstalls missing parts without deleting data. Use it when the row says Broken part or a screen says the setup needs a repair.
- Open the Supabase project row in App → Connections and tap Repair. On the phone, the app’s card in Settings → Apps also has Repair.
- Choose Automatic or Do it myself.
- For Automatic, approve Supabase access, tap Confirm and repair, and wait until it’s done.
Remove
Remove deletes the ops layer from your project entirely. Only the workspace owner can do it.
- On the web, open App → App settings → App and tap Remove. On the phone, tap Remove on the app’s card in Settings → Apps.
- Tap Continue and approve Supabase access.
- The Removal preview lists what is deleted: the
opsschema and its data, the signing key in Vault, the functions and the scheduled jobs. Your own tables, auth users and extensions are kept. - Tap Confirm and remove.
Who can do what
- Update and Repair: the owner and admins.
- Remove: the owner.
- Everyone else can see the project’s state in Connections.