This is an automated email from the ASF dual-hosted git repository.
meonkeys pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/fineract.git
The following commit(s) were added to refs/heads/develop by this push:
new e16a3695dd FINERACT-2619: improve Securing Fineract docs
new fc6f3cc713 Merge pull request #5901 from
meonkeys/readme-docker-prod-caveats
e16a3695dd is described below
commit e16a3695dd8fcd33a6eee7bd3d5b877e04749665
Author: Adam Monsen <[email protected]>
AuthorDate: Wed May 27 11:29:28 2026 -0700
FINERACT-2619: improve Securing Fineract docs
---
README.md | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 8f8b9df742..46ed926cec 100644
--- a/README.md
+++ b/README.md
@@ -155,7 +155,7 @@ We recommend using the JAR instead of the WAR file
deployment, because it's much
How to run using Docker or Podman
---
-It is possible to do a 'one-touch' installation of Fineract using containers
(AKA "Docker").
+It is possible to do a 'one-touch' installation of Fineract using containers
(AKA "Docker") for dev/test convenience and local/offline demos.
This includes the database running in the container.
As prerequisites, you must have `docker` and `docker-compose` installed on
your machine; see
@@ -165,6 +165,9 @@ Alternatively, you can also use
[Podman](https://github.com/containers/libpod)
(e.g. via `dnf install podman-docker`), and [Podman
Compose](https://github.com/containers/podman-compose/)
(e.g. via `pip3 install podman-compose`) instead of Docker.
+> [!CAUTION]
+> Our images are NOT production-ready. For example, notice how the `test`
Spring profile is enabled via `fineract-common.env`, included by
`docker-compose.yml`, but `test` must not be enabled in production. YOU are
responsible for securing your production instances. See [How to run for
production](#how-to-run-for-production).
+
To run a new Fineract instance on Linux you can simply:
```bash
git clone https://github.com/apache/fineract.git
