Deploy a real service, then prove it is running.

1. 1

   Create a project

   In the Midnight console, create or select a workspace, then create one project for the application.

2. 2

   Create an environment

   Add a development or staging environment for the first deploy. Use production only when the host and recovery path are ready.

3. 3

   Create a service

   Add a service within the project. Record the service and environment you will select during linking.

4. 4

   Set runtime needs

   Add variables, a volume, or a domain only when the application needs them. Saving this desired state does not start a deployment.

cd path/to/your/application
midnight login --api-base https://your-midnight.example --email you@example.com
midnight whoami
midnight link
midnight status

midnight link asks you to select the exact project, environment, and service, then writes .midnight/project.json in the current directory. It contains resource context, not your bearer credential.

midnight up

# In another terminal, if you want the persisted build-event stream:
midnight logs -f --build

The source packager permanently excludes .git and .midnight, honors the repository root .gitignore, then applies .midnightignore. The human source upload is limited to 50 MiB compressed.

1. 1

   Operation

   Confirm the operation reaches SUCCEEDED. On failure, keep the request ID, reason code, and final events.

2. 2

   Deployment

   Verify the deployment points to the intended service, environment, source digest, and resulting immutable image.

3. 3

   Health

   Confirm the runtime observation is healthy and the expected container is present on the trusted host.

4. 4

   Route

   If a domain is configured, check Midnight's route state and probe the public hostname separately. Internal route agreement does not prove public DNS.

5. 5

   Logs

   Review build and runtime logs for startup errors without copying secrets into an issue.

midnight status
midnight logs -f
midnight open