polterware/kit

FAQ

Short answers to the recurring questions about Polter, Supabase, packaged apps, and configuration models.

These answers are short on purpose. If you need the full operational detail, follow the linked pages in the rest of the documentation.

Common questions

Can I use Ops without Polter?

Not for the recommended setup, migration, configuration, and installation workflows. The current documentation assumes Polter for those responsibilities.

Do I need Supabase CLI?

Yes for repository and migration workflows. Polter is a workflow layer on top of the Supabase tooling rather than a replacement for the backend itself.

Can I use a packaged app without rebuilding?

Yes. That is exactly what the macOS install workflow is for. Use Polter install and runtime configuration instead of rebuilding.

How do I switch to another Supabase project?

Relink the source checkout with the link workflow and refresh configuration with configure. For packaged apps, refresh the runtime connection rather than rebuilding.

What is the difference between env config and runtime config?

env config is the development fallback used mainly in source checkouts. Runtime config is the persisted desktop connection used by installed apps.

On this page