Installing and running Fineract in production: containers, Kubernetes, PostgreSQL, TLS, AWS and private networks, plus scheduler jobs, COB troubleshooting, backups and configuration.
Moving from the demo docker-compose files to a production container setup: why the published compose files are not production-ready, removing the test profile, tenant database settings through environment variables, logging and upgrades by image tag.
Running Fineract on Kubernetes: the example manifests in the repository, read, write and batch deployments, a separate Liquibase migration job, health checks through the actuator, secrets for tenant databases and rolling upgrades.
Preparing PostgreSQL for Fineract: the tenants database and tenant schemas, connection pooling through HikariCP variables, running in UTC, read replicas for read instances and sizing storage for transaction history.
Putting Fineract behind NGINX or a cloud load balancer: replacing the built-in self-signed certificate, forwarded headers, when to turn off embedded SSL and move to port 8080, and keystore options.
Packaging your own Fineract distribution: a Dockerfile based on apache/fineract, dropping plugin and driver JARs into /app/libs, loader.path, and rebuilding on every Fineract release.
Deploying Fineract on AWS: Amazon RDS or Aurora PostgreSQL, document storage in S3 with instance profile credentials, MSK with IAM authentication for events and COB partitioning, and CloudWatch metrics.
Hosting Fineract without internet exposure: VPN-only access with limited ports, air-gapped back-office accounting, mirroring images and dependencies, and what you lose (payments, notifications) when offline.
Deciding between the Spring Boot JAR and the legacy WAR on an external Tomcat: plugin support, configuration, why the documentation recommends the JAR, and migrating an existing WAR deployment.
Knowing what runs in the background: the Quartz-scheduled jobs, enabling and disabling jobs through global configuration, ordering Loan COB business steps through the API and checking job run history.
Fixing loans that return HTTP 409 or stay locked after Close of Business: soft and hard locks, locks with errors, the bypass flag for repair transactions, orphaned lock cleanup and inline COB for selected loans.
Protecting Fineract data: PostgreSQL dumps versus continuous archiving and point-in-time recovery, backing up the tenants database with every tenant schema, restore testing and recovery objectives for a core banking system.
Sizing HikariCP for Fineract: the FINERACT_HIKARI_* settings, pool sizes per instance type, timeouts during COB, and connection limits on PostgreSQL and read replicas.
Reviewing the global configuration switches that change platform behavior, such as maker-checker, holiday repayment rescheduling, transactions on holidays and job enablement, before go-live and after upgrades.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.