decompose 0.2.1

A simple and flexible scheduler and orchestrator to manage non-containerized applications
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

# Migrating from Docker Compose

`decompose` is designed to feel familiar to Docker Compose users. If you already have a Docker Compose workflow, transitioning to `decompose` is straightforward for local development scenarios where you don't need containerization.

## Key differences

- **No containers** — `decompose` runs native processes directly on your host machine. There are no images to build or pull.
- **No networking abstraction** — Services communicate over localhost. There is no bridge network or DNS-based service discovery.
- **Shell commands** — The `command` field runs a shell command directly, rather than specifying a container entrypoint.
- **No volumes or bind mounts** — Processes access the filesystem directly. Use `working_dir` to control the working directory.

## Translating your Compose file

A Docker Compose service like:

```yaml
services:
  api:
    build: .
    ports:
      - "8080:8080"
    environment:
      DATABASE_URL: postgres://localhost/mydb
    depends_on:
      db:
        condition: service_healthy
```

Becomes:

```yaml
processes:
  api:
    command: "cargo run --release"
    environment:
      DATABASE_URL: postgres://localhost/mydb
    depends_on:
      db:
        condition: process_healthy
```

## Condition mapping

| Docker Compose | decompose |
|----------------|-----------|
| `service_started` | `process_started` |
| `service_completed_successfully` | `process_completed_successfully` |
| `service_healthy` | `process_healthy` |

Full documentation coming soon.