Hi,
I found the code Courage was referring to from here:
https://github.com/Anh3h/fineract-cn-provisioner/commit/2ff842b551a6459e14c8aa1d0aa2a6e85bc622bc
based on this code I just added the needed log statements
to ProvisionerServiceConfig (it already had log statement for timestamp).
Then I
Hi Juhan and Patrick,
Juhan,
Thanks for the feedback on the start-up script. I tried your changes and
the new network name fails on my system. So I added a command to create the
network on the start-up script and used the network in the compose files.
Please try it to verify that it works for you
Be careful, spinning all the containers at the same time required some
resources.
First of all check the CPU and the memory you allocated to docker. I think
by default it is 2GB of ram. it's not enough for all the containers. You
might want to increase it.
I suggest you start with just identity
Hi Patrick,
thanks for the step-by-step instructions. Here are the results:
When I ran "docker-compose up" inside "external-tools" and then "docker
network ls" in another terminal I got:
5271e3e6a6ebexternal-tools_app_net bridge
local
29fa4ca2bf83
Hey Juan,
You should first run the external service before running the main services.
Basically, run the command "docker-compose up" inside the external_tools
folder, or specify the docker-compose file: "docker-compose up -f
./external-toools/docker-compose.yml".
It will spin up cassandra,
Hi!
Courage and Patrick, thanks for explaining to me about the IP addresses
pointing me at the correct repo. Courage, thanks for the recent work on the
repo and for replacing the static IP-s with the service names inside
docker-compose files, I think this increases the readability a lot.
I tried
Hi Patrick,
Thanks for the explanation and I see your point and I think you are right.
Please, can you create a PR on that?
Thanks,
Courage.
On Thu, Jan 3, 2019 at 5:34 PM Patrick Finken
wrote:
> Hello Ange,
>
> That's what I did. I explained that since the containers are within the
> same
Hello Ange,
That's what I did. I explained that since the containers are within the
same network, they could be referenced by their hostname instead of the
IP addresses.
But you right, changing it will break the provision script. Actually, I
didn't use that script (because I'm on a windows
I want to thank everyone for their valuable and transparent discussion on
helping improve the deployability of Fineract CN in the cloud.
The mailing list is the perfect place for an open, back-and-forth
discussion and debate and of course some aspects might get lost in
translation but I don't
Hi Patrick,
Thanks for the explanation. The hardcoded IP addresses are necessary. The
is a provisioner script that uses these addresses to provision the system
after startup. Starting the Fineract CN services is just one part of the
set-up process.
If you read the README you will realize that.
I
Hello Juan,
I used the scripts from this repo:
https://github.com/openMF/fineract-cn-containers which seems to be the more
updated.
You don't need to add all the services to a network because they are
automatically added to the same network as the external services.
If you look a the end of the
Hi Juhan,
Happy New Year. Hope this email finds you well.
On Tue, Jan 1, 2019 at 3:26 PM Juhan Aasaru wrote:
> Hi Patrick and Courage!
>
> Patrick, thanks for sharing the tip how to get the docker-compose version
> of services working without configuring static IP addresses.
> After adding
Hi Patrick and Courage!
Patrick, thanks for sharing the tip how to get the docker-compose version
of services working without configuring static IP addresses.
After adding Fineract microservices to "app_net" network I was
successful using this approach (with one micro service for now - I plan to
Hi Patrick,
Yea, since they are on the same network you can use the hostname instead.
But the docker-compose file is different so you would want to check that
out.
Thanks,
Courage.
On Sun, Dec 30, 2018 at 1:16 PM Patrick Finken
wrote:
> Hey Juhan,
>
> I manage to deploy on docker using the
Hi Juhan,
The Kubernetes scripts should not work correctly 'cause I am still to work
on them, I am moving to a different cloud platform, for some reason, it's
delaying.
Also, you should run the applications locally and they should run
successfully, NOTE THAT I UPDATED THE CODE ON PROVISIONER
Hey Juhan,
I manage to deploy on docker using the script here:
https://github.com/openMF/fineract-cn-containers. It seems to be the same.
Since the containers are part of the same network, actually you don't have
to use the IP addresses. You can directly use the container hostname.
for example
Hi Courage,
I also checked out the work you have done on containers as I also plan to
deploy the Fineract CN services to the cloud. Would you mind explaining a
few things for me:
1. I tried running the scripts (taken from your GitHub fork) locally (I
always find I need to be able to run anything
Hi Patrick,
Could you check this out instead?
https://github.com/Anh3h/fineract-cn-docker-scripts
I am still to merge that into the Mifos codebase
That should work.
Thanks,
Courage.
On Tue, Dec 25, 2018 at 6:04 PM Patrick Finken
wrote:
> Hello Courage,
>
> Actually, the script is from
>
Hello Courage,
Actually, the script is from
https://github.com/openMF/fineract-cn-containers. The problem is that the
provisioner is expecting two properties that are not specified in the
Dockerfile.
provisioner| ***
provisioner| APPLICATION FAILED TO START
Hi Patrick,
You wouldn't want to deactivate it 'cause its needed for authentication.
I containerized Fineract CN as a summer of code project, that should help
you out.
https://github.com/openMF/fineract-cn-containers
Merry Christmas,
Courage.
On Tue, Dec 25, 2018 at 1:22 AM Patrick Finken
20 matches
Mail list logo
