lasta_di.smart.deploy.mode = warm

# Is development environment here? (used for various purpose, you should set false if unknown)
development.here = false

# The title of environment (e.g. local or integration or production)
environment.title = Production

# Does it enable the Framework internal debug? (true only when emergency)
framework.debug = false

Use the following commands to run a standalone MinIO server as a container.

Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication
require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically,

Solr has become a top-level Apache project and main line 
development for Lucene and Solr is happening in each 
project's git repository now:

- Lucene: <https://gitbox.apache.org/repos/asf/lucene.git>
- Solr: <https://gitbox.apache.org/repos/asf/solr.git>

If you're seeing this message then switch the development to 'main':
git checkout main

Development for branch 8x remains in the shared repository:

Where can I get the latest release?
-----------------------------------
You can download the release source from our [download page][maven-download].

Contributing
------------

If you are interested in the development of Maven, please consult the
documentation first and afterward you are welcome to join the developers
mailing list to ask questions or discuss new ideas/features/bugs etc.

Please read the [Development - Contributing](https://fastapi.tiangolo.com/contributing/) guidelines in the documentation site....

    ```

5. Wait for [GitHub Actions][github_actions] to start the publish job.

6. Prepare for ongoing development and push to GitHub.

    ```
    sed -i "" \
      "s/version = \".*\"/version = \"$NEXT_VERSION\"/g" \
      build.gradle.kts
    git commit -am "Prepare next development version."
    git push
    ```

7. Confirm the [GitHub Actions][github_actions] publish job succeeded.

This is in contrast to the **development** stages, where you are constantly changing the code, breaking it and fixing it, stopping and restarting the development server, etc.

## Deployment Strategies { #deployment-strategies }

There are several ways to do it depending on your specific use case and the tools that you use.

Để chạy ứng dụng FastAPI của bạn cho quá trình phát triển (development), bạn có thể sử dụng lệnh `fastapi dev`:

<div class="termy">

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

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

             Searching for package file structure from directories with

If you plan to contribute on a regular basis, please consider filing a [contributor license agreement][cla].

Additional Resources
--------------------

+ [Contributing patches](https://maven.apache.org/guides/development/guide-maven-development.html#Creating_and_submitting_a_patch)
+ [Apache Maven JIRA project page](https://issues.apache.org/jira/projects/MNG/)
+ [Contributor License Agreement][cla]
+ [General GitHub documentation](https://help.github.com/)

    }

    // Test constant field values
    public void xtest_constantFields() {
        assertEquals("lasta_di.smart.deploy.mode", FessEnv.lasta_di_SMART_DEPLOY_MODE);
        assertEquals("development.here", FessEnv.DEVELOPMENT_HERE);
        assertEquals("environment.title", FessEnv.ENVIRONMENT_TITLE);
        assertEquals("framework.debug", FessEnv.FRAMEWORK_DEBUG);