Hi Michael, thanks for your suggestions, maybe I was really overthinking our issue. I fetched the develop branch of Fineract and docker-built it myself, it looks like a working (ok, starting..) Fineract instance really. We'll try to use this self-built version then for now..
cheers, K On Fri, Dec 11, 2020 at 11:07 PM Michael Vorburger <[email protected]> wrote: > Kristóf, the truth is that there actually simply isn't any Fineract 1.4 on > a public the Google Container (Docker) Registry anywhere... ;-) > > For https://www.fineract.dev, as per the earlier thread James posted, I > rebuild it from develop (on every commit to GitHub, fully automated) and > push it to Google Container Registry (because Google Cloud doesn't like to > read directly from Docker Hub). That registry is internal to > https://www.fineract.dev and not public, because normally people don't > need this, as it's also available on > https://hub.docker.com/r/apache/fineract. I could open it up with 1 click > (but would then need to watch costs for egress a bit), but.. is that what > you're looking for, would this help you? I get that impression you want a > "latest stable" release, so you want a 1.4 tag on a registry. > > We actually don't even have a 1.4 on Docker Hub, yet. I had created > https://issues.apache.org/jira/browse/FINERACT-1164 about it a while > back. You basically want that, but on a publicly available Google Cloud > Container Registry, right? But if we do something like this as a project, > it should be automated for all release tags, not a "manual" 1.4.0 I build > and push, that's nonsense. I can try looking into how hard that would over > the coming big break, if that would help you a lot? Are there others > reading this who would use such released (1.4, future 1.5) container > images, if they were available on some repository? Whether Docker Hub or on > Google Cloud registry probably doesn't actually matter, does it, as long as > you can easily "docker pull" it? > > But isn't it simpler for you to simply rebuild from a Git tag inside your > Google Cloud project (like I do for https://www.fineract.dev, but from > develop)? It's not hard. Or am I missing something, or are there any tips I > can share? Again, to be it seems fairly trivial to just selb build whatever > you need, but do let me know if I'm perhaps underestimating the complexity > this causes for end-users here? > > > On Wed, Dec 9, 2020 at 5:46 PM Kristóf Józsa <[email protected]> wrote: > >> Hi Michael, >> >> the question is of course, whether we can get access to the docker images >> of the latest Fineract 1.4 from the Google docker registry. What do we need >> to be able to pull those images and use them in the Mifos Mojaloop Lab >> environments? >> >> thanks, >> K >> >> >> On Wed, Dec 9, 2020 at 5:32 PM James Dailey <[email protected]> >> wrote: >> >>> The team at DPC is working on the mifos payment hub integration with >>> fineract as part of an ongoing demonstration of the full Mifos/Fineract >>> payments lab. (more info on the mifos website) >>> >>> To do that they've been using a snapshot of the dev branch but are >>> shifting to a "latest stable" release strategy. This is for Fineract1.x at >>> this point. i.e. we're moving to upstream. >>> >>> @Michael Vorburger <[email protected]> had mentioned on a thread about >>> docker --> google container registry: >>> >>> http://mail-archives.apache.org/mod_mbox/fineract-dev/202011.mbox/%3cCALiX4iaw_b-PkuSVMTr=caQf2SzSO=aqtwt8evemf_sduwg...@mail.gmail.com%3e >>> <http://mail-archives.apache.org/mod_mbox/fineract-dev/202011.mbox/%3cCALiX4iaw_b-PkuSVMTr=caQf2SzSO=aqtwt8evemf_sduwg...@mail.gmail.com%3e> >>> >>> The need is to pull a stable blob that could be pushed and hosted on >>> Azure or AWS. >>> >>> @kristof - please ask your questions here on list. >>> >>> Thanks, >>> @jdailey <[email protected]> >>> >>>
