from main import app
```

Если структура вашего кода выглядит так:

```
.
├── backend
│   ├── main.py
│   ├── __init__.py
```

Тогда следует указать такой `entrypoint`:

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

что будет эквивалентно:

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

### `fastapi dev` с путём { #fastapi-dev-with-path }

	@(env bash $(PWD)/buildscripts/race.sh)

test-iam: install-race ## verify IAM (external IDP, etcd backends)
	@echo "Running tests for IAM (external IDP, etcd backends)"
	@MINIO_API_REQUESTS_MAX=10000 CGO_ENABLED=0 go test -timeout 15m -tags kqueue,dev -v -run TestIAM* ./cmd
	@echo "Running tests for IAM (external IDP, etcd backends) with -race"

```python
from main import app
```

如果你的程式碼結構像是：

```
.
├── backend
│   ├── main.py
│   ├── __init__.py
```

那你應該把 `entrypoint` 設為：

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

這等同於：

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

### 搭配路徑使用 `fastapi dev` { #fastapi-dev-with-path }

	// is invalid. This function returns success for the
	// most part unless one of the formats is not consistent
	// with expected Erasure format. For example if a user is
	// trying to pool FS backend into an Erasure set.
	if err = checkFormatErasureValues(formatConfigs, storageDisks, setDriveCount); err != nil {
		return nil, err
	}

	// All disks report unformatted we should initialized everyone.

from main import app
```

If your code was structured like:

```
.
├── backend
│   ├── main.py
│   ├── __init__.py
```

Then you would set the `entrypoint` as:

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

which would be equivalent to:

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

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

from main import app
```

Wenn Ihr Code so strukturiert wäre:

```
.
├── backend
│   ├── main.py
│   ├── __init__.py
```

Dann würden Sie den `entrypoint` so setzen:

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

was äquivalent wäre zu:

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

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

from main import app
```

Si tu código estuviera estructurado así:

```
.
├── backend
│   ├── main.py
│   ├── __init__.py
```

Entonces pondrías el `entrypoint` como:

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

lo cual sería equivalente a:

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

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

from main import app
```

Si votre code est structuré comme :

```
.
├── backend
│   ├── main.py
│   ├── __init__.py
```

Alors vous définiriez le `entrypoint` comme :

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

ce qui équivaudrait à :

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

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

from main import app
```

Se o seu código estiver estruturado assim:

```
.
├── backend
│   ├── main.py
│   ├── __init__.py
```

Então você definiria o `entrypoint` como:

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

o que seria equivalente a:

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

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

//
// 5. __missingParts__       - has the latest copy of xl.meta but has some parts
// missing.  This is identified separately since this may need manual
// inspection to understand the root cause. E.g, this could be due to
// backend filesystem corruption.

// listOnlineDisks - returns
// - a slice of disks where disk having 'older' xl.meta (or nothing)
// are set to nil.