client, il échouera en cas de **discordance** dans les données utilisées.

Ainsi, vous **détecterez de nombreuses erreurs** très tôt dans le cycle de développement au lieu d’attendre qu’elles apparaissent pour vos utilisateurs finaux en production puis de tenter de déboguer l’origine du problème. ✨...

      <span style="background-color:#007166"><font color="#D3D7CF"> tip </font></span>  Running in development mode, for production use:
             <b>fastapi run</b>

             Logs:

     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Will watch for changes in these directories:

## Use the `fastapi` CLI

Run the development server on localhost with reload:

```bash
fastapi dev
```


Run the production server:

```bash
fastapi run
```

### Add an entrypoint in `pyproject.toml`

FastAPI CLI will read the entrypoint in `pyproject.toml` to know where the FastAPI app is declared.

```toml

      <plugin>
        <artifactId>maven-source-plugin</artifactId>
        <configuration>
          <excludes>
            <!-- 3. Don't include it in the source jar (since it's really more of a "test" than it is production code). -->
            <exclude>**/ForceGuavaCompilation*</exclude>
            <exclude>**/DummyJavadocClass*</exclude>
          </excludes>
        </configuration>
      </plugin>
      <plugin>

      <span style="background-color:#007166"><font color="#D3D7CF"> tip </font></span>  Running in development mode, for production use:
             <b>fastapi run</b>

             Logs:

     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Will watch for changes in these directories:

```console
$ <font color="#4E9A06">fastapi</font> run --workers 4 <u style="text-decoration-style:solid">main.py</u>

  <span style="background-color:#009485"><font color="#D3D7CF"> FastAPI </font></span>  Starting production server 🚀

             Searching for package file structure from directories with
             <font color="#3465A4">__init__.py</font> files

            if (logger.isDebugEnabled()) {
                logger.debug("Using custom GCS endpoint: {}", endpoint);
            }
        } else {
            // Production: use credentials file or default credentials
            final String credentialsFile = getInitParameter("credentialsFile", null, String.class);
            if (StringUtil.isNotBlank(credentialsFile)) {

            throw new CIFSException("Failed to create multi-channel transport: " + e.getMessage(), e);
        }
    }

    /**
     * Creates a default CIFSContext for multi-channel operations.
     * In a production implementation, this should be replaced with proper context sharing
     * from the main session to ensure consistent authentication and configuration.
     */

      <span style="background-color:#007166"><font color="#D3D7CF"> tip </font></span>  Running in development mode, for production use:
             <b>fastapi run</b>

             Logs:

     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Will watch for changes in these directories:

 * <li>For high-security applications, consider using AES with GCM mode via {@link #setAlgorithm(String)} and {@link #setTransformation(String)}</li>
 * <li>Ensure keys are securely generated and stored</li>
 * <li>For production systems with stringent security requirements, consider using authenticated encryption modes</li>
 * </ul>
 * <p>
 * <strong>Usage Example:</strong>
 * </p>
 * <pre>
 * CachedCipher cipher = new CachedCipher();