[tool.fastapi]
entrypoint = "backend.main:app"
```

이는 다음과 동일합니다:

```python
from backend.main import app
```

### `fastapi dev`에 경로 지정하기 { #fastapi-dev-with-path }

`fastapi dev` 명령어에 파일 경로를 전달할 수도 있으며, 그러면 사용할 FastAPI app 객체를 추정합니다:

```console
$ fastapi dev main.py
```

하지만 매번 `fastapi` 명령어를 호출할 때마다 올바른 경로를 전달해야 합니다.

./mc mb -l myminio/versioned

./mc mirror internal myminio/versioned/ --quiet >/dev/null

## Soft delete (creates delete markers)
./mc rm -r --force myminio/versioned >/dev/null

## mirror again to create another set of version on top
./mc mirror internal myminio/versioned/ --quiet >/dev/null

expected_checksum=$(./mc cat internal/dsync/drwmutex.go | md5sum)

```

Bu da şuna eşdeğer olur:

```python
from backend.main import app
```

### Path ile `fastapi dev` { #fastapi-dev-with-path }

Dosya path'ini `fastapi dev` komutuna da verebilirsiniz; hangi FastAPI app objesini kullanacağını tahmin eder:

```console
$ fastapi dev main.py
```

Ancak `fastapi` komutunu her çağırdığınızda doğru path'i geçmeyi hatırlamanız gerekir.

```

lo cual sería equivalente a:

```python
from backend.main import app
```

### `fastapi dev` con path { #fastapi-dev-with-path }

También puedes pasar el path del archivo al comando `fastapi dev`, y adivinará el objeto app de FastAPI que debe usar:

```console
$ fastapi dev main.py
```

Pero tendrías que recordar pasar el path correcto cada vez que llames al comando `fastapi`.

```

ce qui équivaudrait à :

```python
from backend.main import app
```

### `fastapi dev` avec un chemin { #fastapi-dev-with-path }

Vous pouvez également passer le chemin du fichier à la commande `fastapi dev`, et elle devinera l’objet d’application FastAPI à utiliser :

```console
$ fastapi dev main.py
```

```

o que seria equivalente a:

```python
from backend.main import app
```

### `fastapi dev` com path { #fastapi-dev-with-path }

Você também pode passar o path do arquivo para o comando `fastapi dev`, e ele vai deduzir o objeto de aplicação FastAPI a ser usado:

```console
$ fastapi dev main.py
```

Mas você teria que lembrar de passar o path correto toda vez que chamar o comando `fastapi`.

echo ""
echo "--- get_imagemagick_cmd function tests ---"

# Test that ImageMagick is available (either convert or magick)
if command -v magick >/dev/null 2>&1 || command -v convert >/dev/null 2>&1; then
    echo -e "ImageMagick available: ${GREEN}YES${NC}"

    echo ""
    echo "--- Image thumbnail tests (requires ImageMagick) ---"

    # Test: PNG thumbnail generation

        with:
          enable-cache: true
          cache-dependency-glob: |
            pyproject.toml
            uv.lock
      - name: Install docs extras
        run: uv sync --locked --no-dev --group docs
      - name: Export Language Codes
        id: show-langs
        run: |
          echo "langs=$(uv run ./scripts/docs.py langs-json)" >> $GITHUB_OUTPUT

  build-docs:
    needs:
      - changes

```

which would be equivalent to:

```python
from backend.main import app
```

### `fastapi dev` with path { #fastapi-dev-with-path }

You can also pass the file path to the `fastapi dev` command, and it will guess the FastAPI app object to use:

```console
$ fastapi dev main.py
```

But you would have to remember to pass the correct path every time you call the `fastapi` command.

```

was äquivalent wäre zu:

```python
from backend.main import app
```

### `fastapi dev` mit Pfad { #fastapi-dev-with-path }

Sie können auch den Dateipfad an den Befehl `fastapi dev` übergeben, und er wird das zu verwendende FastAPI-App-Objekt erraten:

```console
$ fastapi dev main.py
```

Aber Sie müssten sich daran erinnern, bei jedem Aufruf des `fastapi`-Befehls den korrekten Pfad zu übergeben.