App Deployment Console

Deployment dashboard

Apps, deployment targets, and live database connections

Choose a database from the list at right to inspect its schemas, then review deployment targets below.

Discovery

Search this Mac for PostgreSQL databases

Viewing

Click a database in Viewing to inspect its schemas, tables, and columns.

Templates

Deployment presets

Reusable

Template name Template slug Description Default API base URL Default DB profile Default schema Branch name Notes

Local Development

Bind a local app to a local database profile and a working schema.

DB profile
Schema
Local URL

Shared Testing

Point testers at a shared server without relying on your machine.

Server IP
Testing URL
Separate DB target

Production

Lock in the online deployment target and final database binding.

Stable URL
Production DB
Strict schema

Templates

Saved templates

Deploy

Deployment targets

Publish

Make the app public on `firstdodo.com`

Save the public URL you want testers to open. For this project, a good starting point is https://app.firstdodo.com.

Point app.firstdodo.com at the server hosting the app.
Use the saved public URL as the link you send to testers.
Keep firstdodo.com for the main site or redirect it to the app URL.

Checklist

How to publish `firstdodo.com`

In GoDaddy DNS, point app.firstdodo.com at the server that runs this app.
Keep the app running in Docker on that server and let Caddy serve it on HTTPS.
Save the public URL here as https://app.firstdodo.com.
Share the saved link with testers, or redirect firstdodo.com to it.

App Deployment DB profile Deployment schema Environment

Public app URL

Branch name Notes

Store separate local, testing, and production targets without losing the database profile link.

Matrix

Deployment matrix

Never

Targets

App deployment targets

Database

Schema and table field counts

0 schemas

Connections

Database profiles

0 profiles

Provisioning

Create the local app database

Creates The Connector and its PG Connect & Deploy schema on your local Postgres server, then adds it as a database profile.

Migrations

Install app tables into The Connector

Runs the app's SQL migrations against The Connector so the app registry, deployments, and templates tables are created.

Database migration

1

Step 1

Choose the local source database

This is the database you are copying from. It only shows local profiles.

Choose a local database.

2

Step 2

Choose the online target database

This is where the migration will land. If this is your first migration, use the create button to provision a new target first.

Choose an online database.

3

Step 3

Pick the source schema and target schema

Compare the schema summaries before choosing. If the target schema does not exist yet, the app will create it during migration.

Source schema Target schema

4

Step 4

Choose what to copy

Use schema only, schema plus data, data only, or selected tables.

Migration mode Selected tables

5

Step 5

Review and run

Confirm the plan, then save or execute the migration.

Notes

First-ever migration: if the online target does not exist yet, create it first with the `+` button, then continue with schema and data steps. `Data only` requires the target schema and tables to already exist.

App migration

App migration

Manage the app registry App to migrate

Use this pane to create, clone, or delete app records separately from the database migration itself.

Transfer

Create an app transfer plan

Move a selected app from one connected database profile to another and save the plan for later execution.

App to transfer Source database profile Source schema Target database profile Target schema Notes

New app

Create an app for migration

App name

App slug

Description

Default destination database connection

Default schema in that destination database

Why separate it?

App migration stays optional

The database flow handles schema and data. The app flow handles registry records and target bindings.