Postpiece Support and Contact Guide

Contact and support

Postpiece environments are typically operated by the team deploying them. For access, publishing, or configuration issues, start with the workspace owner or deployment operator for your environment.

Operational support

If you are working in an internal or local deployment, contact the maintainer responsible for that stack. They control identity settings, environment variables, and domain mappings.

If you are reviewing the codebase itself, document reproducible issues with the route, environment, and failing flow so they can be addressed in the correct app boundary.

Before filing a bug

Capture whether the issue is in apps/website, apps/api, or apps/sites, and verify the related local service ports are healthy.

For media and upload issues specifically, confirm MinIO is running locally and that the API and frontloader point at the same bucket configuration.

Useful debugging context

Include the exact route, whether the failure happened in the dashboard or a hosted site, and whether the issue reproduced in raw SSR output or only after client hydration.

For auth-sensitive routes such as /dash, note whether the problem occurs before sign-in, after sign-in, or only when Clerk has finished loading the session.