Commands

Every jadpo command, what it does and how to run it.

The jadpo command

You work with Jadpo through one command, jadpo, and a short list of subcommands.

Commands for looking into and changing code

These commands show you what your code does: its routes, the SQL its queries send, and what a prompt sends a model.

Commands for the database, settings and translations

These commands change what sits beside your code: the database's migrations, your local settings, and the wording of your app in each language.

Commands for records, findings and review

Some files in your project are records: files Jadpo writes for you to commit, such as the record of your public API, which a reviewer reads in a pull request (Review and records).

Commands for background work

These commands are for an operator: the person who looks after a running app.

Commands for packages

A package is code you install rather than write: a library, or a provider package that calls an outside service such as Stripe (External services).

Commands for services, calls, email and stored data

These commands change a feature flag while your app runs, show what your app sent outside while you develop it, the provider calls and the email, and check a deploy before it happens.

Commands for debugging, editors and help

jadpo why <schedule> ends with the schedule's .jadpo place, and takes --json (Watching schedules).