onvibe.run
← All forkable apps
shelflife

Track food expiry dates so nothing in your pantry goes to waste.

What a fork includes

You get

  • All the code (19 files)
  • Database schema — tables & structure, no rows
  • 2 public assets (shared)
  • Your own fresh app at a new URL

Stays with the owner

  • Database rows / data
  • Private user uploads
  • Environment secrets (API keys)
assets.ts8.7 KB
assets_spa.ts13.9 KB
auth.ts5.4 KB
config.ts795 B
db.ts17.0 KB
js/app.ts3.2 KB
js/datefmt.ts2.2 KB
js/store.ts3.9 KB
js/sync.ts2.6 KB
js/ui.ts38.6 KB
main.ts16.8 KB
migrations/20260618090000_push_alerts.sql1.1 KB
migrations/20260619180000_offline_sync.sql1.2 KB
migrations/20260619210000_lists.sql2.0 KB
migrations/20260622000000_password_reset.sql498 B
onvibe.json166 B
push.ts4.7 KB
shell.ts6.0 KB
views.ts20.5 KB
Fork it with your AI

onvibe apps are forked through an AI assistant connected to onvibe. Paste this into a chat (e.g. Claude with the onvibe connector) and it will create your copy:

Fork the onvibe app "shelflife" into my account. Call fork_project with source_project_id "shelflife" and a new_project_id I choose. It copies the code, the database schema (structure only, no rows) and the public assets — not the data, private uploads or secrets. After forking, run check_app and tell me the new live URL.

New here? See the sharing & forking guide.