Next steps, by what you want to do

You have a server, an application and a way back. Here is where each next thing is.

Deploy more kinds of application

• Your stack, its build and start commands: Deploy by stack and Build and start commands.
• Several applications from one repository: Monorepos.
• A Docker Compose project: Docker Compose.
• A Dockerfile or a registry image: Container applications.
• A site that already runs on the server: Adopt a site.
• A preview for each pull request: Previews.

Domains and network

• Aliases, wildcards and the DNS check: Domains.
• Where certificates come from, and your own: Certificates.
• Who may reach a site, real client addresses, TCP and UDP ports: Network.

Data

• Engines, versions, instances, users and imports: Databases.
• Destinations, schedules, and bringing back a whole server: Backups and disaster recovery.

Automate

• Deploy from CI with a token: Deploy from a pipeline.
• A server written down in Git: The manifest.
• Operate a server from your laptop: Operate a server from elsewhere.
• Terraform and OpenTofu, or Python: Terraform, Python client.

A team

• Accounts, roles, approvals and the audit log: Security.
• Teams, projects and environments: Teams.
• Single sign-on, LDAP and SCIM: Single sign-on.
• The console on a name of its own, over HTTPS: Reaching the console.

Several servers

• A central, from a container on a NAS or a VPS: Running a central.

When something goes wrong

• noust diagnose DOMAIN names the most likely cause first.
• Troubleshooting has the frequent failures, each with its message and its fix.

Look it up

Every command, every API operation, every setting, and what changed in each release.