"configuration-problems-base",
          "javadoc",
          "kotlin-dsl-provider-plugins",
          "precondition-tester",
          "test-suites-base",
          "worker-main",
          "workers"
        ],
        "parallelizationMethod": {
          "numberOfBatches": 1,
          "name": "TeamCityParallelTests"
        }
      },
      {
        "subprojects": [

		workers = workers[:len(workers)-1]
		worker <- expiryOp(nil)
		es.stats.workers.Add(-1)
	}
	// Atomically replace workers.
	es.workers.Store(&workers)
}

// Worker handles 4 types of expiration tasks.
// 1. Expiry of objects, includes regular and transitioned objects
// 2. Expiry of noncurrent versions due to NewerNoncurrentVersions

RUN pip install --no-cache-dir --upgrade -r /code/requirements.txt

COPY ./app /code/app

# (1)!
CMD ["fastapi", "run", "app/main.py", "--port", "80", "--workers", "4"]
```

1. Burada worker sayısını 4 yapmak için `--workers` komut satırı seçeneğini kullanıyoruz.

Bunun mantıklı olabileceği birkaç örnek:

#### Basit Bir Uygulama { #a-simple-app }

Here are some possible combinations and strategies:

* **Uvicorn** with `--workers`
    * One Uvicorn **process manager** would listen on the **IP** and **port**, and it would start **multiple Uvicorn worker processes**.
* **Kubernetes** and other distributed **container systems**

And if you need to have multiple workers, you can simply use the `--workers` command line option.

/// note | Technical Details

The Docker image was created when Uvicorn didn't support managing and restarting dead workers, so it was needed to use Gunicorn with Uvicorn, which added quite some complexity, just to have Gunicorn manage and restart the Uvicorn worker processes.

因此，这种情况下你**不希望**在容器内再启多个 workers（例如通过 `--workers` 命令行选项）。你会希望每个容器仅有一个**单独的 Uvicorn 进程**（但可能会有多个容器）。

在容器内再放一个进程管理器（就像启多个 workers 一样）只会引入**不必要的复杂性**，而这些你很可能已经在集群系统中处理了。

### 具有多个进程和特殊情况的容器 { #containers-with-multiple-processes-and-special-cases }

当然，也有一些**特殊情况**，你可能希望让**一个容器**里运行多个 **Uvicorn worker 进程**。

在这些情况下，你可以使用 `--workers` 命令行选项来设置要运行的 worker 数量：

```{ .dockerfile .annotate }
FROM python:3.14

Donc, dans ce cas, vous **ne voudrez pas** avoir plusieurs workers dans le conteneur, par exemple avec l'option de ligne de commande `--workers`. Vous voudrez avoir **un seul processus Uvicorn** par conteneur (mais probablement plusieurs conteneurs).

            <option value="$PROJECT_DIR$/platforms/jvm/code-quality-workers" />
            <option value="$PROJECT_DIR$/platforms/jvm/distributions-jvm" />
            <option value="$PROJECT_DIR$/platforms/jvm/ear" />
            <option value="$PROJECT_DIR$/platforms/jvm/groovy-compiler-worker" />
            <option value="$PROJECT_DIR$/platforms/jvm/groovydoc-worker" />
            <option value="$PROJECT_DIR$/platforms/jvm/jacoco" />

Aquí hay algunas combinaciones y estrategias posibles:

* **Uvicorn** con `--workers`
    * Un administrador de procesos de Uvicorn **escucharía** en la **IP** y **puerto**, y iniciaría **múltiples worker processes de Uvicorn**.
* **Kubernetes** y otros sistemas de **contenedor distribuidos**

Y si necesitas tener múltiples workers, puedes simplemente utilizar la opción de línea de comandos `--workers`.

/// note | Detalles Técnicos

La imagen de Docker se creó cuando Uvicorn no soportaba gestionar y reiniciar workers muertos, por lo que era necesario usar Gunicorn con Uvicorn, lo que añadía bastante complejidad, solo para que Gunicorn gestionara y reiniciara los worker processes de Uvicorn.