Hi Juhan, I think you are right and it is time to rewrite the build instructions for Fineract CN to adopt the Docker approach. Anyone interested in doing this work?
On Fri, Dec 6, 2019 at 7:50 AM Juhan Aasaru <aas...@gmail.com> wrote: > Hi! > > The problem with npm is caused by the fact that you have not cd into > correct directory. > The instructions under step #4 have this: cd into > ‘integration-tests/fineract-cn-fims-web-app' > > Anyway, we can all agree that the build instructions of Fineract-CN are > almost impossible to properly follow. > And actually there is no need to use demo server. Demo server sets up the > system but > its quite untransparent and difficult to understand for a newcomer. Don't > get me wrong, it > is a great resource afterwards when learning how to call micro services > from code and > how to use listeners. > > To set up the system for the first time I recommend to use Docker-Compose > with Postman instead: > > https://github.com/apache/fineract-cn-docker-compose#2-deploy-fineract-manually-using-postman > This is all tested several times and should work like a charm. > > The following is an idea of mine that is not anywhere documented yet due > to lack of time. > Based on Docker-Compose process we could also create instructions where > micro services are not > started within Docker but they are started directly (run from IDE or java > -jar ...). > > Docker-Compose instructions include creating .env file with common > properties (and RSA keys). > To run micro services directly basically a similar file should be created, > let's call it applciation-locally.yml > and then when starting apps this file should be passed as flag: > --spring.config.location=../application-locally.yml > > Provisioning is be done with Postman (see instructions at > fineract-cn-docker-compose) > - this way one understands better what steps are taking place during > provisioning. > > Kind regards > Juhan > > > > > > > > Kontakt Awasum Yannick (<yannickawa...@gmail.com>) kirjutas kuupäeval R, > 6. detsember 2019 kell 04:35: > >> Why are you running npm (x) on a non node, non js repo (demo-server) ? >> >> The timeout might be showing a lack of memory problem. What is the >> capacity of your machine? >> >> On Thu, Dec 5, 2019 at 9:40 PM Rohit Jain <rohit.j...@esgyn.com> wrote: >> >>> Thanks guys! >>> >>> >>> >>> I think I got off the track right at the beginning of *Step 3: >>> Orchestrate Microservices Using The Demo-server*. It said “… *consider* >>> manually orchestrating …”. I thought I *needed to* go to >>> https://github.com/vishwasbabu/ProvisioningFineractCN. That is where >>> it says start ActiveMQ. Which is why I did. I abandoned that effort when >>> I realized that “consider” meant optional, and I did not really need to do >>> that, since that whole key generation was getting a bit complicated on >>> Windows 10. But then ActiveMQ was still running when I proceeded with the >>> rest of the instructions to build. My bad! >>> >>> Because I had started ActiveMQ, initially demo-server immediately >>> complained about not being able to use port 61616. In fact, the >>> instructions say that this port should not be in use before starting >>> demo-server. I guess I did not pay attention to that part until I got that >>> error. I then stopped ActiveMQ, changed the port 61616 it was using, to >>> 61615, and restarted it (doh!). Demo-server then ran for a long time. But >>> then it gave me a slew of *connection refused* errors for port 61616, >>> even though ActiveMQ was not using it, and *not that the port was being >>> used*. >>> >>> >>> >>> Regardless, I stopped ActiveMQ and this time ran with Command II in the >>> documentation. I did not run into the connection refused error! >>> >>> This time I got some [DicoverClient-*n*] errors that >>> c.n.discovery.TimedSupervisorTask >>> – task supervisor timed out >>> >>> >>> >>> But demo-server kept going after those timeouts and has now been running >>> for 3 hours with no message "INFO o.e.jetty.server.AbstractConnector - >>> StoppedServerConnector@1bdb0376{HTTP/1.1,[http/1.1]}" written to any of >>> the logs as yet. I guess I should have direct standard out to a log since >>> it does not seem to be capturing everything in the logs and I might have >>> just missed that message. >>> >>> >>> >>> I decided to proceed to step 4 but I get the following when I run npm i … >>> >>> c:\Apps\fineract-cn-demo-server>npm i >>> >>> npm WARN saveError ENOENT: no such file or directory, open >>> 'c:\Apps\fineract-cn-demo-server\package.json' >>> >>> npm notice created a lockfile as package-lock.json. You should commit >>> this file. >>> >>> npm WARN enoent ENOENT: no such file or directory, open >>> 'c:\Apps\fineract-cn-demo-server\package.json' >>> >>> npm WARN fineract-cn-demo-server No description >>> >>> npm WARN fineract-cn-demo-server No repository field. >>> >>> npm WARN fineract-cn-demo-server No README data >>> >>> npm WARN fineract-cn-demo-server No license field. >>> >>> >>> >>> up to date in 0.843s >>> >>> found 0 vulnerabilities >>> >>> >>> >>> c:\Apps\fineract-cn-demo-server>npm run dev >>> >>> npm ERR! code ENOENT >>> >>> npm ERR! syscall open >>> >>> npm ERR! path c:\Apps\fineract-cn-demo-server\package.json >>> >>> npm ERR! errno -4058 >>> >>> npm ERR! enoent ENOENT: no such file or directory, open >>> 'c:\Apps\fineract-cn-demo-server\package.json' >>> >>> npm ERR! enoent This is related to npm not being able to find a file. >>> >>> npm ERR! enoent >>> >>> >>> >>> There us a package-lock.json but no package.json. >>> >>> >>> >>> *From:* Ebenezer Graham <ebenezergraha...@gmail.com> >>> *Sent:* Thursday, December 5, 2019 7:39 AM >>> *To:* Awasum Yannick <yannickawa...@gmail.com> >>> *Cc:* dev@fineract.apache.org; Ebenezer Graham <egraha...@alustudent.com >>> > >>> *Subject:* Re: help jump starting? >>> >>> >>> >>> Thanks Awasum for the response. I think that's the issue too >>> >>> >>> >>> @Rohit, it's not necessary to configure a standalone ActiveMQ when >>> running the demo-server. This library ( >>> https://github.com/apache/fineract-cn-command) helps to set up an >>> embedded broker. >>> >>> >>> >>> Also, what is the state of this issue >>> https://github.com/flyway/flyway/issues/2103 >>> >>> >>> >>> Warm regards. >>> >>> >>> >>> On Thu, Dec 5, 2019 at 11:07 AM Awasum Yannick <yannickawa...@gmail.com> >>> wrote: >>> >>> Hi >>> >>> >>> >>> Demo server at times runs with an embedded activemq and other data >>> stores. So if you already have an activemq installed on your host, then >>> thats what is causing the port in use exception. >>> >>> >>> >>> Hope this helps. >>> >>> >>> >>> On Wed, Dec 4, 2019, 23:06 Rohit Jain <rohit.j...@esgyn.com> wrote: >>> >>> Hi Ebenezer, >>> >>> >>> >>> A thread by the same subject line was initiated by my colleague, Eric >>> Owhadi, on 06 Jun, 20:51. He ran into an issue: >>> >>> Could not connect to broker URL: tcp://localhost:61616. Reason: >>> java.net.ConnectException: Connection refused >>> >>> >>> >>> It so happens that 4 months later I have run into the exact same issue. >>> Except that I am running everything on my Windows 10 laptop. Also, I >>> installed and ran ActiveMQ on my laptop. In fact, the demo server got an >>> error initially since it found that port 61616 was being used. So, I >>> modified the activemq.xml file to change that port to avoid the conflict. >>> Then the demo server started all the application services, and then at the >>> end ran into the error above. >>> >>> >>> >>> You responded to Eric and said that you would provide a resolution to >>> this problem. Don’t know if you have a resolution that I can use to move >>> forward. The Demo server created the appropriate databases and keyspaces >>> in PostgreSQL and Cassandra respectively. >>> >>> >>> >>> Rohit >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> *Best Regards,* >>> >>> *Ebenezer Graham* >>> >>> *BSc (Hons) Computing* >>> >>> >>> >>> [image: EmailSignature.png] >>> >>> >>> >>> GitHub <https://ebenezergraham.me> | LinkedIn >>> <https://www.linkedin.com/in/ebenezer-graham/> | Personal Website >>> <https://ebenezergraham.me> >>> >>> skype: >>> >>> ebenezer.graham >>> >>> | Phone: >>> >>> +230 5840 9206 <+230%205840%209206> >>> >>> >>> >>> *“Talk is cheap, show me the Code” *- *Linus Torvalds* >>> >>>
