![ReDoc](https://fastapi.tiangolo.com/img/index/index-02-redoc-simple.png)

## Собрать Docker-образ для однофайлового FastAPI { #build-a-docker-image-with-a-single-file-fastapi }

Если ваше приложение FastAPI — один файл, например `main.py` без директории `./app`, структура файлов может быть такой:

```
.
├── Dockerfile

Aqui estão alguns exemplos de quando isso pode fazer sentido:

#### Um Aplicativo Simples { #a-simple-app }

Você pode querer um gerenciador de processos no contêiner se seu aplicativo for **simples o suficiente** para rodar em um **único servidor**, não em um cluster.

#### Docker Compose { #docker-compose }

        assertTrue(result.contains(Hexdump.toHexString(TEST_INFO_LEVEL, 3)));
    }

    @Test
    void testToStringWithDifferentPaths() {
        // Test with various path formats
        String[] testPaths = { "simple.txt", "path/to/file.doc", "//server/share/file.txt", "folder\\windows\\style.txt", "" // empty path
        };

        for (String path : testPaths) {

And the `dict` you receive as `weights` will actually have `int` keys and `float` values.

///

## Recap { #recap }

With **FastAPI** you have the maximum flexibility provided by Pydantic models, while keeping your code simple, short and elegant.

But with all the benefits:

* Editor support (completion everywhere!)
* Data conversion (a.k.a. parsing / serialization)
* Data validation
* Schema documentation

![Swagger UI](https://fastapi.tiangolo.com/img/index/index-01-swagger-ui-simple.png)

### 可选的 API 文档

访问 <a href="http://127.0.0.1:8000/redoc" class="external-link" target="_blank">http://127.0.0.1:8000/redoc</a>。

你会看到另一个自动生成的文档（由 <a href="https://github.com/Rebilly/ReDoc" class="external-link" target="_blank">ReDoc</a> 生成）：

![ReDoc](https://fastapi.tiangolo.com/img/index/index-02-redoc-simple.png)

## 示例升级

import org.mockito.InOrder;
import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;

import jcifs.CIFSException;

@ExtendWith(MockitoExtension.class)
class SSPContextTest {

    // Simple, deterministic test double covering all methods of SSPContext.
    private static class DummySSPContext implements SSPContext {
        private byte[] signingKey;
        private boolean established;

    // Concrete implementation for testing abstract NtlmMessage
    private static class TestNtlmMessage extends NtlmMessage {
        @Override
        public byte[] toByteArray() throws IOException {
            // Simple implementation for testing purposes
            return new byte[0];
        }
    }

    @BeforeEach
    void setUp() {
        message = new TestNtlmMessage();
    }

    @Test

            return resource;
        }
    }

    @BeforeEach
    void setUp() {
        lenient().when(fileEntry.getName()).thenReturn("test");
    }

    @Test
    @DisplayName("Iterator without filter - simple case")
    void iteratorWithoutFilter() {
        // Setup: constructor calls advance() once
        when(delegate.hasNext()).thenReturn(true, false);
        when(delegate.next()).thenReturn(fileEntry);

import org.mockito.InOrder;
import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;

@ExtendWith(MockitoExtension.class)
class FileEntryTest {

    @Mock
    FileEntry mockEntry;

    // Simple fake implementation to exercise the interface without mocks
    private static final class TestFileEntry implements FileEntry {
        private final String name;
        private final int type;

/// danger

Never store user's plaintext passwords. Always store a "secure hash" that you can then verify.

If you don't know, you will learn what a "password hash" is in the [security chapters](security/simple-oauth2.md#password-hashing){.internal-link target=_blank}.

///

## Multiple models { #multiple-models }