Choosing the right type keeps deploy intent clear for everyone on the team.
Use when: You created the project in Optizen yourself.
Deploy commands are fully under your control. Use this when you know exactly what needs to run.
Use when: The project was discovered via server scan.
Review the suggested metadata carefully before relying on it. Scan results are a starting point, not a source of truth.
Use when: Deploys are driven by docker compose.
Set the working directory to where your compose file lives on the server. Commands like docker compose pull and docker compose up -d are typical.
Use when: Deploys pull or run a container image directly.
Works best when your image reference is stable and tags are meaningful (not just "latest").
Use when: The project manages reverse proxy config — Caddy, Nginx, etc.
Label these explicitly so they are not confused with normal app deploys. They often need special care around reload commands.
Use when: Your workflow does not fit the other categories.
Full control over all deploy commands. Good for scripts, static sites, or anything non-standard.