Re: fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[Yemdjih Kaze Nasser]

Nice work. Thanks again for your great contributions.

On Sun, May 17, 2020, 12:33 Awasum Yannick  wrote:

> Congratulations Mike. This is very good work and will improve the project
> as a whole. This is the way to run Enterprise Applications in the 2020s.
>
> On Sun, May 17, 2020 at 12:20 PM Michael Vorburger 
> wrote:
>
>> Hello everyone,
>>
>> I'm happy to share that https://www.fineract.dev now always
>> automatically updates itself from the very latest source code available on
>> the develop branch of Fineract! (I actually used to manually update it
>> before.)
>>
>> New deployments take about 15’ after any of our great committer merges
>> Pull Requests from you - our contributors. Something that is pretty cool is
>> that on https://demo.fineract.dev/fineract-provider/actuator/info anyone
>> can now actually see the exact Git commit revision that is currently
>> running (this is based on FINERACT-883
>> ).
>>
>> If you are curious about some of the technical details involved here
>> behind the scenes,
>> http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html
>> may interest you. You can see one part of what my blog post describes in
>> live action on https://github.com/apache/fineract/actions - note the new
>> "Deploy to https://www.fineract.dev; workflow, driven by
>> https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml
>> .
>>
>> Something perhaps worth pointing out here is that this is based on modern
>> cloud native CI/CD... to users, it's made to look like the "server" never
>> "stops". Incoming API HTTP traffic is transparently switched over from old
>> to new runtimes. So as you use fineract.dev, it's now entirely possible
>> that, following the merge of a Pull Request, in one instant you hit "old"
>> code, but your next API request hits "new" code that just got deployed!
>> Cool, right?
>>
>> I'm hoping this makes Fineract.dev even more useful to the community, and
>> will serve both as a showcase for the project, as well as be of value e.g.
>> for your QA. (Should you have an interest in a non-demo more stable hosted
>> instance of Apache Fineract, please reach out to me privately - I'm
>> interested in learning more about the need and expectations in this space.)
>>
>> Stay safe & keep hacking and contributing!
>>
>> Best,
>> M.
>> ___
>> Michael Vorburger
>> http://www.vorburger.ch
>>
>

Re: fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[Frank Nkuyhaga]

Good stuff Michael! This is a great stride!

> On 17 May 2020, at 14:45, Yemdjih Kaze Nasser  wrote:
> 
> Nice work. Thanks again for your great contributions. 
> 
> On Sun, May 17, 2020, 12:33 Awasum Yannick  > wrote:
> Congratulations Mike. This is very good work and will improve the project as 
> a whole. This is the way to run Enterprise Applications in the 2020s. 
> 
> On Sun, May 17, 2020 at 12:20 PM Michael Vorburger  > wrote:
> Hello everyone,
> 
> I'm happy to share that https://www.fineract.dev  
> now always automatically updates itself from the very latest source code 
> available on the develop branch of Fineract! (I actually used to manually 
> update it before.)
> 
> New deployments take about 15’ after any of our great committer merges Pull 
> Requests from you - our contributors. Something that is pretty cool is that 
> on https://demo.fineract.dev/fineract-provider/actuator/info 
>  anyone can now 
> actually see the exact Git commit revision that is currently running (this is 
> based on FINERACT-883 ).
> 
> If you are curious about some of the technical details involved here behind 
> the scenes, 
> http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html 
> 
>  may interest you. You can see one part of what my blog post describes in 
> live action on https://github.com/apache/fineract/actions 
>  - note the new "Deploy to 
> https://www.fineract.dev " workflow, driven by 
> https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml
>  
> .
> 
> Something perhaps worth pointing out here is that this is based on modern 
> cloud native CI/CD... to users, it's made to look like the "server" never 
> "stops". Incoming API HTTP traffic is transparently switched over from old to 
> new runtimes. So as you use fineract.dev , it's now 
> entirely possible that, following the merge of a Pull Request, in one instant 
> you hit "old" code, but your next API request hits "new" code that just got 
> deployed! Cool, right?
> 
> I'm hoping this makes Fineract.dev even more useful to the community, and 
> will serve both as a showcase for the project, as well as be of value e.g. 
> for your QA. (Should you have an interest in a non-demo more stable hosted 
> instance of Apache Fineract, please reach out to me privately - I'm 
> interested in learning more about the need and expectations in this space.)
> 
> Stay safe & keep hacking and contributing!
> 
> Best,
> M.
> ___
> Michael Vorburger
> http://www.vorburger.ch 

Re: fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[Natasha Natarajan]

Congratulations, Michael!

On Sun, May 17, 2020 at 5:20 AM Michael Vorburger  wrote:

> Hello everyone,
>
> I'm happy to share that https://www.fineract.dev now always automatically
> updates itself from the very latest source code available on the develop
> branch of Fineract! (I actually used to manually update it before.)
>
> New deployments take about 15’ after any of our great committer merges
> Pull Requests from you - our contributors. Something that is pretty cool is
> that on https://demo.fineract.dev/fineract-provider/actuator/info anyone
> can now actually see the exact Git commit revision that is currently
> running (this is based on FINERACT-883
> ).
>
> If you are curious about some of the technical details involved here
> behind the scenes,
> http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html
> may interest you. You can see one part of what my blog post describes in
> live action on https://github.com/apache/fineract/actions - note the new
> "Deploy to https://www.fineract.dev; workflow, driven by
> https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml
> .
>
> Something perhaps worth pointing out here is that this is based on modern
> cloud native CI/CD... to users, it's made to look like the "server" never
> "stops". Incoming API HTTP traffic is transparently switched over from old
> to new runtimes. So as you use fineract.dev, it's now entirely possible
> that, following the merge of a Pull Request, in one instant you hit "old"
> code, but your next API request hits "new" code that just got deployed!
> Cool, right?
>
> I'm hoping this makes Fineract.dev even more useful to the community, and
> will serve both as a showcase for the project, as well as be of value e.g.
> for your QA. (Should you have an interest in a non-demo more stable hosted
> instance of Apache Fineract, please reach out to me privately - I'm
> interested in learning more about the need and expectations in this space.)
>
> Stay safe & keep hacking and contributing!
>
> Best,
> M.
> ___
> Michael Vorburger
> http://www.vorburger.ch
>

Re: fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[Frank Nkuyahaga]

Good stuff Michael! This is a great stride

> On 17 May 2020, at 14:45, Yemdjih Kaze Nasser  wrote:
> 
> Nice work. Thanks again for your great contributions. 
> 
> On Sun, May 17, 2020, 12:33 Awasum Yannick  > wrote:
> Congratulations Mike. This is very good work and will improve the project as 
> a whole. This is the way to run Enterprise Applications in the 2020s. 
> 
> On Sun, May 17, 2020 at 12:20 PM Michael Vorburger  > wrote:
> Hello everyone,
> 
> I'm happy to share that https://www.fineract.dev  
> now always automatically updates itself from the very latest source code 
> available on the develop branch of Fineract! (I actually used to manually 
> update it before.)
> 
> New deployments take about 15’ after any of our great committer merges Pull 
> Requests from you - our contributors. Something that is pretty cool is that 
> on https://demo.fineract.dev/fineract-provider/actuator/info 
>  anyone can now 
> actually see the exact Git commit revision that is currently running (this is 
> based on FINERACT-883 ).
> 
> If you are curious about some of the technical details involved here behind 
> the scenes, 
> http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html 
> 
>  may interest you. You can see one part of what my blog post describes in 
> live action on https://github.com/apache/fineract/actions 
>  - note the new "Deploy to 
> https://www.fineract.dev " workflow, driven by 
> https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml
>  
> .
> 
> Something perhaps worth pointing out here is that this is based on modern 
> cloud native CI/CD... to users, it's made to look like the "server" never 
> "stops". Incoming API HTTP traffic is transparently switched over from old to 
> new runtimes. So as you use fineract.dev , it's now 
> entirely possible that, following the merge of a Pull Request, in one instant 
> you hit "old" code, but your next API request hits "new" code that just got 
> deployed! Cool, right?
> 
> I'm hoping this makes Fineract.dev even more useful to the community, and 
> will serve both as a showcase for the project, as well as be of value e.g. 
> for your QA. (Should you have an interest in a non-demo more stable hosted 
> instance of Apache Fineract, please reach out to me privately - I'm 
> interested in learning more about the need and expectations in this space.)
> 
> Stay safe & keep hacking and contributing!
> 
> Best,
> M.
> ___
> Michael Vorburger
> http://www.vorburger.ch 

Re: fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[Manthan Surkar]

Congratulations Michael, great work!

On Sun, May 17, 2020 at 6:04 PM Frank Nkuyhaga  wrote:

> Good stuff Michael! This is a great stride!
>
> On 17 May 2020, at 14:45, Yemdjih Kaze Nasser 
> wrote:
>
> Nice work. Thanks again for your great contributions.
>
> On Sun, May 17, 2020, 12:33 Awasum Yannick  wrote:
>
>> Congratulations Mike. This is very good work and will improve the project
>> as a whole. This is the way to run Enterprise Applications in the 2020s.
>>
>> On Sun, May 17, 2020 at 12:20 PM Michael Vorburger 
>> wrote:
>>
>>> Hello everyone,
>>>
>>> I'm happy to share that https://www.fineract.dev now always
>>> automatically updates itself from the very latest source code available on
>>> the develop branch of Fineract! (I actually used to manually update it
>>> before.)
>>>
>>> New deployments take about 15’ after any of our great committer merges
>>> Pull Requests from you - our contributors. Something that is pretty cool is
>>> that on https://demo.fineract.dev/fineract-provider/actuator/info
>>> anyone can now actually see the exact Git commit revision that is currently
>>> running (this is based on FINERACT-883
>>> ).
>>>
>>> If you are curious about some of the technical details involved here
>>> behind the scenes,
>>> http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html
>>> may interest you. You can see one part of what my blog post describes in
>>> live action on https://github.com/apache/fineract/actions - note the
>>> new "Deploy to https://www.fineract.dev; workflow, driven by
>>> https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml
>>> .
>>>
>>> Something perhaps worth pointing out here is that this is based on
>>> modern cloud native CI/CD... to users, it's made to look like the "server"
>>> never "stops". Incoming API HTTP traffic is transparently switched over
>>> from old to new runtimes. So as you use fineract.dev, it's now entirely
>>> possible that, following the merge of a Pull Request, in one instant you
>>> hit "old" code, but your next API request hits "new" code that just got
>>> deployed! Cool, right?
>>>
>>> I'm hoping this makes Fineract.dev even more useful to the community,
>>> and will serve both as a showcase for the project, as well as be of value
>>> e.g. for your QA. (Should you have an interest in a non-demo more stable
>>> hosted instance of Apache Fineract, please reach out to me privately - I'm
>>> interested in learning more about the need and expectations in this space.)
>>>
>>> Stay safe & keep hacking and contributing!
>>>
>>> Best,
>>> M.
>>> ___
>>> Michael Vorburger
>>> http://www.vorburger.ch
>>>
>>
>

fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[Michael Vorburger]

Hello everyone,

I'm happy to share that https://www.fineract.dev now always automatically
updates itself from the very latest source code available on the develop
branch of Fineract! (I actually used to manually update it before.)

New deployments take about 15’ after any of our great committer merges Pull
Requests from you - our contributors. Something that is pretty cool is that
on https://demo.fineract.dev/fineract-provider/actuator/info anyone can now
actually see the exact Git commit revision that is currently running (this
is based on FINERACT-883
).

If you are curious about some of the technical details involved here behind
the scenes,
http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html
may interest you. You can see one part of what my blog post describes in
live action on https://github.com/apache/fineract/actions - note the new
"Deploy to https://www.fineract.dev; workflow, driven by
https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml
.

Something perhaps worth pointing out here is that this is based on modern
cloud native CI/CD... to users, it's made to look like the "server" never
"stops". Incoming API HTTP traffic is transparently switched over from old
to new runtimes. So as you use fineract.dev, it's now entirely possible
that, following the merge of a Pull Request, in one instant you hit "old"
code, but your next API request hits "new" code that just got deployed!
Cool, right?

I'm hoping this makes Fineract.dev even more useful to the community, and
will serve both as a showcase for the project, as well as be of value e.g.
for your QA. (Should you have an interest in a non-demo more stable hosted
instance of Apache Fineract, please reach out to me privately - I'm
interested in learning more about the need and expectations in this space.)

Stay safe & keep hacking and contributing!

Best,
M.
___
Michael Vorburger
http://www.vorburger.ch

Re: [Mifos-developer] fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[Sendoro Juma]

Nice piece of work; 

Thanks a lot for the contribution.

---

On 2020-05-17 14:19, Michael Vorburger wrote:

> Hello everyone, 
> 
> I'm happy to share that https://www.fineract.dev now always automatically 
> updates itself from the very latest source code available on the develop 
> branch of Fineract! (I actually used to manually update it before.) 
> 
> New deployments take about 15' after any of our great committer merges Pull 
> Requests from you - our contributors. Something that is pretty cool is that 
> on https://demo.fineract.dev/fineract-provider/actuator/info anyone can now 
> actually see the exact Git commit revision that is currently running (this is 
> based on FINERACT-883 [1]). 
> 
> If you are curious about some of the technical details involved here behind 
> the scenes, 
> http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html 
> may interest you. You can see one part of what my blog post describes in live 
> action on https://github.com/apache/fineract/actions - note the new "Deploy 
> to https://www.fineract.dev; workflow, driven by 
> https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml.
>  
> 
> Something perhaps worth pointing out here is that this is based on modern 
> cloud native CI/CD... to users, it's made to look like the "server" never 
> "stops". Incoming API HTTP traffic is transparently switched over from old to 
> new runtimes. So as you use fineract.dev [2], it's now entirely possible 
> that, following the merge of a Pull Request, in one instant you hit "old" 
> code, but your next API request hits "new" code that just got deployed! Cool, 
> right? 
> 
> I'm hoping this makes Fineract.dev even more useful to the community, and 
> will serve both as a showcase for the project, as well as be of value e.g. 
> for your QA. (Should you have an interest in a non-demo more stable hosted 
> instance of Apache Fineract, please reach out to me privately - I'm 
> interested in learning more about the need and expectations in this space.) 
> 
> Stay safe & keep hacking and contributing! 
> 
> Best, 
> M.
> ___
> Michael Vorburger
> http://www.vorburger.ch 
> Mifos-developer mailing list
> mifos-develo...@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
 

Links:
--
[1] https://issues.apache.org/jira/browse/FINERACT-883
[2] http://fineract.dev

Re: fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[Awasum Yannick]

Congratulations Mike. This is very good work and will improve the project
as a whole. This is the way to run Enterprise Applications in the 2020s.

On Sun, May 17, 2020 at 12:20 PM Michael Vorburger 
wrote:

> Hello everyone,
>
> I'm happy to share that https://www.fineract.dev now always automatically
> updates itself from the very latest source code available on the develop
> branch of Fineract! (I actually used to manually update it before.)
>
> New deployments take about 15’ after any of our great committer merges
> Pull Requests from you - our contributors. Something that is pretty cool is
> that on https://demo.fineract.dev/fineract-provider/actuator/info anyone
> can now actually see the exact Git commit revision that is currently
> running (this is based on FINERACT-883
> ).
>
> If you are curious about some of the technical details involved here
> behind the scenes,
> http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html
> may interest you. You can see one part of what my blog post describes in
> live action on https://github.com/apache/fineract/actions - note the new
> "Deploy to https://www.fineract.dev; workflow, driven by
> https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml
> .
>
> Something perhaps worth pointing out here is that this is based on modern
> cloud native CI/CD... to users, it's made to look like the "server" never
> "stops". Incoming API HTTP traffic is transparently switched over from old
> to new runtimes. So as you use fineract.dev, it's now entirely possible
> that, following the merge of a Pull Request, in one instant you hit "old"
> code, but your next API request hits "new" code that just got deployed!
> Cool, right?
>
> I'm hoping this makes Fineract.dev even more useful to the community, and
> will serve both as a showcase for the project, as well as be of value e.g.
> for your QA. (Should you have an interest in a non-demo more stable hosted
> instance of Apache Fineract, please reach out to me privately - I'm
> interested in learning more about the need and expectations in this space.)
>
> Stay safe & keep hacking and contributing!
>
> Best,
> M.
> ___
> Michael Vorburger
> http://www.vorburger.ch
>

Updates to staging.mifos.io and mobile.mifos.io

[Terence Monteiro]

Folks,

I'm pleased to inform that the latest Community App with latest Fineract
backend is now live on https://staging.mifos.io . This implements
authentication changes effected by
https://issues.apache.org/jira/browse/FINERACT-726 which removes the
username/password sent as URL parameters. This is based on the current
develop branch of the Community App and Apache Fineract repos. Likewise,
https://mobile.mifos.io now has the latest from develop branch.

For updating both these projects, I have applied DB migrations on the
existing data. A key incompatibility of the old DB was that self service
user mappings had duplicate client ids in the
table m_selfservice_user_client_mapping and the same table has been rid of
duplicate client_id mappings (different login users mapped same client) by
retaining the first mapped login user to the client and deleting the
remaining references. Anyone using https://mobile.mifos.io to test the self
service functionality, please check if the login you're using still works
as before and let me know otherwise.

-Terence Monteiro

Git Error

[Natasha Natarajan]

Hi All,


I am an Outreachy Summer intern. Last month, I submitted PRs which have
already been merged into the develop.


Today, in terminal, when I was attempting to push changes up, I am get an
error. I am able to pull but not push.



ERROR: Permission to apache/fineract.git denied to nnatarajan.

fatal: Could not read from remote repository.


Please make sure you have the correct access rights

and the repository exists.




Your guidance is appreciated.


Thank you,

Natasha

Re: [Mifos-developer] fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[qwert test]

Thanks for the update

On Sun, May 17, 2020, 4:50 PM Michael Vorburger  wrote:

> Hello everyone,
>
> I'm happy to share that https://www.fineract.dev now always automatically
> updates itself from the very latest source code available on the develop
> branch of Fineract! (I actually used to manually update it before.)
>
> New deployments take about 15’ after any of our great committer merges
> Pull Requests from you - our contributors. Something that is pretty cool is
> that on https://demo.fineract.dev/fineract-provider/actuator/info anyone
> can now actually see the exact Git commit revision that is currently
> running (this is based on FINERACT-883
> ).
>
> If you are curious about some of the technical details involved here
> behind the scenes,
> http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html
> may interest you. You can see one part of what my blog post describes in
> live action on https://github.com/apache/fineract/actions - note the new
> "Deploy to https://www.fineract.dev; workflow, driven by
> https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml
> .
>
> Something perhaps worth pointing out here is that this is based on modern
> cloud native CI/CD... to users, it's made to look like the "server" never
> "stops". Incoming API HTTP traffic is transparently switched over from old
> to new runtimes. So as you use fineract.dev, it's now entirely possible
> that, following the merge of a Pull Request, in one instant you hit "old"
> code, but your next API request hits "new" code that just got deployed!
> Cool, right?
>
> I'm hoping this makes Fineract.dev even more useful to the community, and
> will serve both as a showcase for the project, as well as be of value e.g.
> for your QA. (Should you have an interest in a non-demo more stable hosted
> instance of Apache Fineract, please reach out to me privately - I'm
> interested in learning more about the need and expectations in this space.)
>
> Stay safe & keep hacking and contributing!
>
> Best,
> M.
> ___
> Michael Vorburger
> http://www.vorburger.ch
> Mifos-developer mailing list
> mifos-develo...@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: Git Error

[Natasha Natarajan]

Thank you, Yemdjih! It has been a short while. With your help, I was able
to submit PR.


On Sun, May 17, 2020 at 9:37 PM Yemdjih Kaze Nasser 
wrote:

> Hello Natasha,
>
> You cannot push code directly to apache/fineract.git without committer
> privileges.
> What you can do is push to your forked remote repository then create a PR.
>
> This probably happening cause you are trying to push directly to
> apache/fineract instead of your remote fork
>
> Hope this helps.
>
> On Mon, 18 May 2020 at 04:04, Natasha Natarajan <
> natashanatara...@gmail.com> wrote:
>
>> Hi All,
>>
>>
>> I am an Outreachy Summer intern. Last month, I submitted PRs which have
>> already been merged into the develop.
>>
>>
>> Today, in terminal, when I was attempting to push changes up, I am get an
>> error. I am able to pull but not push.
>>
>>
>>
>> ERROR: Permission to apache/fineract.git denied to nnatarajan.
>>
>> fatal: Could not read from remote repository.
>>
>>
>> Please make sure you have the correct access rights
>>
>> and the repository exists.
>>
>>
>>
>>
>> Your guidance is appreciated.
>>
>>
>> Thank you,
>>
>> Natasha
>>
>

Re: Git Error

[Yemdjih Kaze Nasser]

Hello Natasha,

You cannot push code directly to apache/fineract.git without committer
privileges.
What you can do is push to your forked remote repository then create a PR.

This probably happening cause you are trying to push directly to
apache/fineract instead of your remote fork

Hope this helps.

On Mon, 18 May 2020 at 04:04, Natasha Natarajan 
wrote:

> Hi All,
>
>
> I am an Outreachy Summer intern. Last month, I submitted PRs which have
> already been merged into the develop.
>
>
> Today, in terminal, when I was attempting to push changes up, I am get an
> error. I am able to pull but not push.
>
>
>
> ERROR: Permission to apache/fineract.git denied to nnatarajan.
>
> fatal: Could not read from remote repository.
>
>
> Please make sure you have the correct access rights
>
> and the repository exists.
>
>
>
>
> Your guidance is appreciated.
>
>
> Thank you,
>
> Natasha
>

Re: Git Error

[Yemdjih Kaze Nasser]

Glad I could help.

On Mon, 18 May 2020 at 05:22, Natasha Natarajan 
wrote:

> Thank you, Yemdjih! It has been a short while. With your help, I was able
> to submit PR.
>
>
> On Sun, May 17, 2020 at 9:37 PM Yemdjih Kaze Nasser 
> wrote:
>
>> Hello Natasha,
>>
>> You cannot push code directly to apache/fineract.git without committer
>> privileges.
>> What you can do is push to your forked remote repository then create a PR.
>>
>> This probably happening cause you are trying to push directly to
>> apache/fineract instead of your remote fork
>>
>> Hope this helps.
>>
>> On Mon, 18 May 2020 at 04:04, Natasha Natarajan <
>> natashanatara...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>>
>>> I am an Outreachy Summer intern. Last month, I submitted PRs which have
>>> already been merged into the develop.
>>>
>>>
>>> Today, in terminal, when I was attempting to push changes up, I am get
>>> an error. I am able to pull but not push.
>>>
>>>
>>>
>>> ERROR: Permission to apache/fineract.git denied to nnatarajan.
>>>
>>> fatal: Could not read from remote repository.
>>>
>>>
>>> Please make sure you have the correct access rights
>>>
>>> and the repository exists.
>>>
>>>
>>>
>>>
>>> Your guidance is appreciated.
>>>
>>>
>>> Thank you,
>>>
>>> Natasha
>>>
>>