Applications

Applications list

• URL: https://console.outplane.com/applications
• Table shows name, repository, build method (Dockerfile / Buildpack), last commit (with time‑ago), and deployment status.
• Toolbar: search, status filter, and Deploy Application button to start a new app.
• Row actions (Overflow): Runtime Logs, HTTP Logs, Deployments, Settings, Environment, Monitoring, Delete.
• Pagination defaults to 20 rows; adjust or filter by status to narrow results.
• Empty state (no apps) surfaces quick actions: deploy app, create database, map domain, or storage (coming soon).

Create an application

1. Open Applications → Deploy Application or go directly to https://console.outplane.com/applications/create-app.
2. Source: choose Git Provider (GitHub).
   • If the GitHub App is not installed, you’ll be prompted to install it. The callback is handled at /hooks/github.
   • Pick a repo from the list (search + account filter). The table shows repo name, privacy, default branch.
3. Branch & root directory: branches are auto‑loaded; defaults to main/master. Use the file browser to pick a subdirectory if needed.
4. App name: auto‑generated from the repo; you can edit it. Naming is used in domains and internal IDs.
5. Build method: Dockerfile or Paketo Buildpacks. Directory/build/install commands can be edited later in Build Settings.
   • Dockerfile builds respect .dockerignore. Keep dependencies/cache out of the build context for faster, smaller images.
   • Buildpack is zero‑config for common stacks (Node, Go, Python, etc.).
6. Resources: choose an instance type (e.g., op‑20 free, op‑46 2 vCPU/4 GB, op‑82/op‑94 enterprise). Set Min/Max scale (0–10; min=0 enables scale‑to‑zero).
7. Environment variables (optional): add key/value pairs before first deploy. The platform will honor a PORT env var—if your app reads PORT, listen on it; otherwise set the port to match your server.
8. Deploy: creates the app and kicks off the first deployment. You’re redirected to the deployment detail page with live build logs.

PaaS tips

• Follow 12-factor style: write logs to stdout/stderr (they are streamed to Monitoring and per-app logs), avoid local disk for state, and configure your server to listen on PORT.
• Keep Docker contexts lean (.dockerignore); prefer multi-stage builds to produce small runtime images.
• Use buildpack for quick starts; switch to Dockerfile for custom build steps or multi-service repos.

Navigating into an app

• Clicking a row opens the per‑app side navigation with Overview, Deployment, Runtime Logs, HTTP Logs, Settings.