Hello everyone
How can one add this as part of the documentation for Fineract. I'm certain 
there'd be a lot of requests similar to this in the future.

> On 6 Jan 2021, at 05:58, Chairul Akmal <[email protected]> wrote:
> 
> Great!
> 
> Thanks Petri for your answer. Yes, actually that was what I were looking for.
> 
> Regards
> Chairul
> 
>> On 2021/01/05 23:00:04, Petri Tuomola <[email protected]> wrote: 
>> Hi Chairul
>> 
>> I hope I understood your question correctly - but if you are asking where 
>> can you set the connection parameters for the different tenant databases, 
>> please look at the table tenant_server_connections on the database 
>> fineract_tenants
>> 
>> The columns schema_server, schema_server_port, schema_name, 
>> schema_connection_parameters in that table are used to construct the 
>> connection string for each tenant database as follows:
>> 
>>        String jdbcUrl = 
>> this.driverConfig.constructProtocol(tenantConnectionObj.getSchemaServer(),
>>                tenantConnectionObj.getSchemaServerPort(), 
>> tenantConnectionObj.getSchemaName(),
>>                tenantConnectionObj.getSchemaConnectionParameters());
>> 
>> So if you want to change the server / schema name for a specific tenant, try 
>> updating the relevant row in the table fineract_tenants.
>> 
>> Hope this helps
>> 
>> Regards
>> Petri
>> 
>>>> On 5 Jan 2021, at 8:55 PM, Chairul Akmal <[email protected]> 
>>>> wrote:
>>> 
>>> Hi Michael,
>>> 
>>> Thank you so much for your response.
>>> 
>>> I think my question was not clear. Sorry about that. What I meant was the 
>>> database (DB) name for the default tenant itself, "fineract_default". 
>>> Unlike for "fineract_tenants" that accept database url (which contains the 
>>> DB name) as env var, FINERACT_DEFAULT_TENANTDB only accept hostname and 
>>> port. So, my question is rather, does fineract require the tenant database 
>>> to be named "fineract_default"? Is there a way to use different tenant DB 
>>> name without changing the codebase?
>>> 
>>> Thank you for understanding.
>>> 
>>> Update: Thankfully, I have managed to connect the docker image with 
>>> database (by naming the tenant DB `fineract_default`). There are some 
>>> problem with database migrations where V1 failed with `(SQL State: 42S02 - 
>>> Error Code: 1051)`, looks like related to the jdbc driver. But this is a 
>>> different problem. :)
>>> 
>>> Cheers,
>>> Chairul
>>> 
>>> On 2021/01/04 17:32:11, Michael Vorburger <[email protected]> wrote: 
>>>> Chairul,
>>>> 
>>>> you're ALMOST ;) there - note how in
>>>> https://github.com/apache/fineract/blob/develop/docker-compose.yml#L45
>>>> there is BOTH the fineract_tenants_* but ALSO the
>>>> FINERACT_DEFAULT_TENANTDB_* env vars? The latter is what you are looking
>>>> for!
>>>> 
>>>> HTH & makes sense?
>>>> 
>>>> M.
>>>> 
>>>> PS: Would someone be willing to contribute better documentation about this?
>>>> Ideally via a PR to
>>>> https://github.com/apache/fineract/blob/develop/README.md, or
>>>> https://github.com/apache/fineract/tree/develop/fineract-doc/src/docs/en.
>>>> 
>>>> _______________________
>>>> Michael Vorburger
>>>> http://www.vorburger.ch
>>>> 
>>>> 
>>>> On Mon, Jan 4, 2021 at 5:42 PM Chairul Akmal <[email protected]>
>>>> wrote:
>>>> 
>>>>> Hi folks,
>>>>> 
>>>>> I am a new fineract user and have been recently trying to deploy fineract
>>>>> 1.4.0 on Digital Ocean. The plan that I currently have is to deploy
>>>>> apache/fineract docker image and connect to managed MySQL database from
>>>>> Digital Ocean. However, I have been struggling with connecting fineract
>>>>> with the non-local database.
>>>>> 
>>>>> I understand that there are ways to modify the `fineract_tenants` database
>>>>> from environmental variables (e.g. in docker-compose.yml), however can I 
>>>>> do
>>>>> the same with `fineract_default`? The way I see it, `fineract_default` is
>>>>> hard-coded a lot in source code and I wanted to modify it, unfortunately I
>>>>> can't find any documentations on fineract database setup/schema. I tried
>>>>> googling around for old mifos documentations but most of them are
>>>>> deprecated or inaccessible anymore.
>>>>> 
>>>>> Cheers,
>>>>> Chairul
>>>>> 
>>>> 
>> 
>> 

Reply via email to