CLI

onebase <command> [flags]

#Flags

Each flag can also be set with an environment variable, which can come from a .env file.

#Environment variables

#doctor

✗ error posts.ts:2: Imports from the convex package instead of onebase.
         fix: Use "./_generated/server" for query/mutation/action and "onebase/values" for v.
✗ error schema.ts › posts.index("by_athor"): Field "athor" doesn't exist on "posts".
         fix: Known fields: title, author
⚠ warn  posts.ts › add: mutation has no args validator, so any input is accepted.
         fix: Add args: { ... } (use args: {} if it takes none).

doctor checks:

• files that fail to load
• index fields that don't exist, and duplicate or reserved index names
• v.id() pointing at missing tables
• functions without args
• crons that call missing functions
• imports from convex/*
• "use node"
• .filter(doc => doc.x === …) mistakes
• stale _generated/ files
• a SQLite database (--db, or <data>/db.sqlite) where deleted documents left a lot of free space

#vacuum

SQLite doesn't shrink its file when documents are deleted: it keeps the free pages and reuses them for new writes. A database created by this version of onebase gives them back by itself. Every 5 minutes, once free pages are at least 64 MB and a quarter of the file, the server frees up to 256 MB, in small slices so writes keep going. The same pass cuts the WAL file back to nothing. Databases created by older versions can't do this until they've been vacuumed once:

onebase vacuum --data ./onebase_data

vacuum rewrites the whole file, so it needs about as much free disk as the data takes up. Writes wait while it runs, so stop the server first. onebase doctor tells you when it's worth running.