/dbflute_mysql/log/*.log
/dbflute_oracle/log/*.log
/src/main/webapp/WEB-INF/conf/*.properties
/src/main/webapp/WEB-INF/db/*.lock.db
/src/main/webapp/WEB-INF/logs/fess*
/.settings/
.project
.classpath
*.iml
.idea
.vscode
.DS_Store
/plugins/
/modules/
/tomcat.8080/
dbflute_fess/output/doc/lastadoc-fess.html
dbflute_fess/schema/project-lastadoc-fess.json

**/target/**
.project
.classpath
.settings/
.svn/

# Intellij
*.ipr
*.iml
.idea
!.idea/icon.png
/bootstrap
/dependencies.xml
.java-version
.checkstyle
.factorypath
repo/

# VSCode
.vscode/

# Mac

/target/
/.settings/
.project
.classpath
*.iml
.idea
.DS_Store
.repository
/.vscode

.classpath
.kotlin
.project
.settings
.gradle
eclipsebin

bin
gen
build
out
lib
generated

target
pom.xml.*
release.properties
local.properties

.idea
*.iml
*.ipr
*.iws
*.log
classes

obj

.DS_Store

# Special Mkdocs files
docs/4.x
docs/changelog.md
docs/contributing.md
docs/index.md

# jenv
/.java-version
/site/

## Storage usage

The selection of varying data and parity drives has a direct impact on the drive space usage. With storage class, you can optimize for high
redundancy or better drive space utilization.

To get an idea of how various combinations of data and parity drives affect the storage usage, let’s take an example of a 100 MiB file stored

| [`Kubernetes`](https://docs.min.io/community/minio-object-store/operations/deployments/kubernetes.html)                                |

## Why is MinIO cloud-native?

* Uvicorn (used by Starlette and **FastAPI**)

///

/// check | Inspired **FastAPI** to

Exist.

The idea of declaring multiple things (data validation, serialization and documentation) with the same Python types, that at the same time provided great editor support, was something I considered a brilliant idea.

 See the License for the specific language governing permissions and
 limitations under the License.
-->
Contributing to Apache Maven
======================

You have found a bug or you have an idea for a cool new feature? Contributing
code is a great way to give something back to the open source community. Before
you dig right into the code, there are a few guidelines that we need

## Deployment Concepts { #deployment-concepts }

These examples run the server program (e.g Uvicorn), starting **a single process**, listening on all the IPs (`0.0.0.0`) on a predefined port (e.g. `80`).

This is the basic idea. But you will probably want to take care of some additional things, like:

* Security - HTTPS
* Running on startup
* Restarts
* Replication (the number of processes running)
* Memory

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 }

Here's a general idea of how the models could look like with their password fields and the places where they are used:

{* ../../docs_src/extra_models/tutorial001_py310.py hl[7,9,14,20,22,27:28,31:33,38:39] *}


/// info