Previews
Try every change before it ships
Each change can run as its own live copy of your product, with its own link. Open it on your laptop or your phone, click around, and ask the agent for changes until it’s right.
-
per change
A preview for each thread
When an agent pushes a change, the preview rebuilds. The last working version stays open while a newer one gets ready.
-
status
It says plainly where it’s at
The thread tells you whether its preview is ready, still preparing, or has failed. A failed one has a Try again button, and the agent can read why it failed.
-
test data
Its own data
A preview can run your setup and seed steps, so it starts with a database of its own and never touches production.
-
tidy
It shuts itself down
Previews stop when the pull request merges, when the thread is archived, or after six hours without use.
for engineers
Two lines if you have a Dockerfile
Add .patchwell/preview.yml to your repository. If your app builds from a Dockerfile, this is enough:
version: 2
build: {dockerfile: Dockerfile, port: 3000}
With Compose and a database
version: 2
app:
compose: [compose.yml]
routes:
- {service: web, port: 3000}
The app is told its own address in PATCHWELL_PREVIEW_URL. Setup, migrate and seed steps, extra routes and subdomains are in the docs.