```python
from main import app
```

Se o seu código estivesse 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 caminho { #fastapi-dev-with-path }

# Security - First Steps { #security-first-steps }

Let's imagine that you have your **backend** API in some domain.

And you have a **frontend** in another domain or in a different path of the same domain (or in a mobile application).

And you want to have a way for the frontend to authenticate with the backend, using a **username** and **password**.

We can use **OAuth2** to build that with **FastAPI**.

# Sécurité - Premiers pas { #security-first-steps }

Imaginons que vous ayez votre API de **backend** sur un certain domaine.

Et vous avez un **frontend** sur un autre domaine ou dans un chemin différent du même domaine (ou dans une application mobile).

Et vous voulez que le **frontend** puisse s'authentifier auprès du **backend**, en utilisant un **username** et un **password**.

Nous pouvons utiliser **OAuth2** pour construire cela avec **FastAPI**.

E para comunicar usando WebSockets com seu backend, você provavelmente usaria as utilidades do seu frontend.

Ou você pode ter um aplicativo móvel nativo que se comunica diretamente com seu backend WebSocket, em código nativo.

Ou você pode ter qualquer outra forma de comunicar com o endpoint WebSocket.

---

```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 }

```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 }

```python
from main import app
```

Si tu código estuviera estructurado así:

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

Entonces establecerí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 }

- For instructions on using KES for encrypting the MinIO backend, follow the [KMS Quick Start](https://github.com/minio/minio/tree/master/docs/kms). The SSE-S3 configuration setup also supports MinIO KMS backend encryption.

## FAQ

> Why is this change needed?

Before, there were two separate mechanisms - S3 objects got encrypted using a KMS,

        int length = testBlock.encode(buffer, 0);

        assertTrue(length > 0);
        assertNull(testBlock.getAndx()); // andx should be cleared when batching disabled
    }

    @Test
    @DisplayName("Test encode with andx command and batching enabled")
    void testEncodeWithAndxBatchingEnabled() {
        when(mockConfig.isUseBatching()).thenReturn(true);
        when(mockAndxCommand.getCommand()).thenReturn(0x42);

│   │   ├── CurlResponse.java      # Response wrapper (implements Closeable)
│   │   ├── CurlException.java     # Unchecked exception for HTTP errors
│   │   └── io/
│   │       ├── ContentCache.java       # In-memory or file-based caching
│   │       └── ContentOutputStream.java # Threshold-based output stream
│   └── test/java/org/codelibs/curl/
│       ├── CurlTest.java          # Factory method tests
│       ├── CurlRequestTest.java   # Request builder tests