palisadeDownload
Docs menu

Run, notebooks, databases

Run and debug configurations, Jupyter notebooks on local kernels, and Postgres and SQLite access.

The rest of the workbench sits one step behind the Fleet board and Review lane. You reach it from any thread or diff.

Run and debug

  • Saved run configurations.
  • Debug adapter discovery.
  • Start and stop.
  • Breakpoints and stepping.
  • Stack and variable inspection.
  • Expression evaluation.
  • Program output.

Notebooks

Jupyter notebook files open as cell-based documents. They run on local kernel processes.

You can edit, run, interrupt, restart, and save them.

Databases

Palisade connects to Postgres and SQLite.

  • Browse the schema.
  • Page through data grids.
  • Run SQL queries.
  • Stage row edits and preview the SQL they produce.
  • Apply edits in a transaction.
  • Catch conflicts with optimistic checks.
  • Confirm before running statements that look destructive.

Credentials

Database passwords go in the macOS credential store when it is available. If Palisade has to fall back to a user-only local file, it tells you. Secrets never enter logs.

Connection records live in Palisade-managed storage, outside your repository.