Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

How to run fineract-cn public Docker images

Running with Docker Compose

Docker-compose scripts for conveniently running a set of fineract Cloud Native micro services are available here.

There are also Postman scripts available to provision the micro services after one has started them.

Running individual images

There are public repositories in DockerHub for fineract-cn: 

This is currently work in progress: 

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFINCN-170
Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyINFRA-18516

How to run fineract-cn public Docker images

There are public repositories in DockerHub for fineract-cn: 

Temporary URL for setting up (this column be deleted once the job is completed)aasaru-provisioner
Micro serviceApache URL https://cloud.docker.com/repository/docker/apache/fineract-cn-fims-web-app/tags


Running a micro service public image

TODO - replace "aasaru" with "apache" once the set-up has been completed

...

docker run apache/fineract-cn-

...

xxx:latest

Or if you want to run specific version

docker run

...

 apache/fineract-cn-

...

xxx:version

...

.number

...

.goes-here

You need to generate keys and pass them to docker images as environmental variables. See these instructions.https://github.com/apache/fineract-cn-docker-compose


How the Docker Hub has been set up


Autobuild has been configured for these repositories with following setup:to follow the same principles as already used with publishing to JFrog Artifactory - this means that one can trigger a build by pushing to branch "develop"

...

and by creating a release (tag) in Github. The only exception is that pushing to other branches besides "develop" doesn't trigger creating image in Docker Hub.

Dockerhub autobuild configuration:

Docker Tag

Source
Comment
Image name
latestdevelop

apache/fineract-cn-projectname:latest

build everything pushed to "develop" branch and publish it under latest tag
Previous build is overwritten.

release-{sourceref}

/^REL([0-9.]+)$/

configured for other rules to work. no
-Without this configuration Docker Hub doesn't work. No build should actually trigger this.

{\1}-{\2}

/^([0-9.]+)-([0-9A-Za-z.]+)$/

Github version tag becomes image name. For example:

  • apache/fineract-cn-projectname:1.3.5-M.1
  • apache/fineract-cn-projectname:1.5.7-RC.1
  • apache/fineract-cn-projectname:1.5.7.1-RC.1
  • apache/fineract-cn-projectname:2.0.0-RELEASE
Tag name has to follow versioning scheme of fineract-cn projects (see README.md of each repo).

{\1}.{\2}.{\3}

/^([0-9]+)\.([0-9]+)\.([0-9]+)$/

{\1}.{\2}.{\3

}.{\4

}

/^([0-9]+)\.([0-9]+)\.([0-9]+)

\.([0-9]+)$/

$/

Github version tag becomes image name. For example:

  • apache/fineract-cn-projectname:2.0.0"
Tag name has to follow versioning scheme of fineract-cn projects.


For autobuild to work the Dockerfile of each  each repository has been split into two stages:

  • build stage - builds the jar. Only the jar is passed to the run stage.
  • run stage - runs the jar built