Simuzo
Compose projects list Manage multi-container projects as a single unit.

Projects vs single containers

Compose projects group one or more services (web, db, redis, …) defined in a compose file. Deploy, stop, and recreate them together. Prefer projects for anything more complex than a single ephemeral container.

Manage Projects

Open Container Manager → Manage Projects (act=list_compose) to:

  • See project name and status
  • Start / stop / recreate project actions
  • Edit the project in the compose editor
  • Delete a project you no longer need

Compose New Project / editor

Compose editor Compose editor for services, environment, ports, and volumes.

Open Compose New Project (act=compose) or edit an existing project.

Ways to start

  • Blank project — define services manually
  • From App Catalog — prefilled YAML/services from a template
  • Edit existing — load project YAML + env file

What you configure per service

FieldDescription
Service nameInternal compose service key
ImageImage reference (optionally from a saved registry)
Container nameOptional explicit name
Restart policyno / always / on-failure (always recommended for apps)
PortsContainer port + optional domain proxy / path
EnvironmentKey/value config and secrets
VolumesNamed volumes or bind mounts

YAML vs visual editing

Depending on complexity, the editor may present a structured service form and/or raw compose YAML. Complex files can open in a text-oriented mode — validate carefully before deploy.

Deploy workflow

1

Define services

Add images, env, and volumes. Attach proxies for public HTTP services.

2

Save & deploy

Deployment often runs as a background task. Wait for completion.

3

Verify

Check Manage Containers for each service, then hit the proxied URL.

Project actions

ActionUse when
StartBring a stopped project up
StopTake the whole stack down
Recreate / redeployApply image or config changes
DeleteRemove stack definition (confirm volumes first)
Stateful services Put MySQL/Postgres data on a named volume before the first deploy so recreates do not wipe the database.

Related