CBSNexora/cbsnexora-backend
4
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

FINERACT-2067: (doc) fix some typos in fineract-doc module.

Browse Source
This commit is contained in:
zeyad2003
2024-03-19 13:42:45 +01:00
committed by Peter Bagrij
parent d955bc26cb
commit 6b94192ac6
19 changed files with 30 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fineract-doc/src/docs/en/chapters/deployment/https.adoc
+1 -1
View File
@@ -8,6 +8,6 @@ For production deployments, we recommend running Fineract behind a modern manage
Such products, when correctly configured, add the conventional `X-Forwarded-For` and `X-Forwarded-Proto` HTTP headers, which Fineract (or rather the Spring Framework really) correctly respects since https://issues.apache.org/jira/browse/FINERACT-914[FINERACT-914 was fixed].
Alternatively, you could replace the built-in default SSL certificate with one you obtained from a Certificate Authority. We currently do not document how to do this, because we do not recommend this approach, as its cumbersome to configure and support and less secure than a managed auto rotating solution.
Alternatively, you could replace the built-in default SSL certificate with one you obtained from a Certificate Authority. We currently do not document how to do this, because we do not recommend this approach, as it's cumbersome to configure and support and less secure than a managed auto rotating solution.
The Fineract API client supports an insecure mode (`FineractClient.Builder#insecure()`), and API users such as mobile apps may expose Settings to let end-users accept the self signed certificate. This should always be used for testing only, never in production.
fineract-doc/src/docs/en/chapters/deployment/instance-type.adoc
+2 -2
View File
@@ -98,7 +98,7 @@ The best practice is to deploy 1 master batch instance and multiple worker batch
| |
+----------------+
----
These soultions can be mixed with each other, based on the load of the Fineract deployment.
These solutions can be mixed with each other, based on the load of the Fineract deployment.
== Configuring instance type via environment variables
@@ -140,7 +140,7 @@ The distinction whether something is a write API can be decided based on the HTT
=== Batch job APIs are allowed only for batch instances
A Fineract instance is ONLY able to serve batch API calls when it’s configured as a batch instance. In read or write instance mode, it won’t serve batch API calls.
If the batch APIs won't be served and and a proper HTTP status code will be returned.
If the batch APIs won't be served and a proper HTTP status code will be returned.
If it’s a batch instance, the batch APIs will be served.
== Batch jobs