# How to fork a local & cloud app nowadays?

**URL:** <https://community.homey.app/t/how-to-fork-a-local-cloud-app-nowadays/66973>\
**Category:** Developers\
**Created:** [August 5, 2022, 8:40pm UTC](https://community.homey.app/t/how-to-fork-a-local-cloud-app-nowadays/66973 "2022-08-05T20:40:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Brandhorst](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chris_brandhorst/32/12449_2.png) [@Chris\_Brandhorst](https://community.homey.app/u/Chris_Brandhorst)\
**Post date:** [August 5, 2022, 8:40pm UTC](https://community.homey.app/t/how-to-fork-a-local-cloud-app-nowadays/66973/1 "2022-08-05T20:40:23Z")

</div>

Back in 2019, I modified an existing app for my personal project (and eventually contributed to it), simply by:

- Forking the repo
- Making the necessary changes
- Installing the app on Homey
- Happy days

Everything is a few years older now, and the app in question is now a hybrid local & cloud app: all devices have both platforms, and the main class extends OAuth2App. When I try to run this, I get an error because the OAuth2 CLIENT\_ID and SECRET are not set in an env.json file, which indeed they are not: I (of course) don’t have them, because it is not my app.

But now I am a bit stumped on how to proceed. I tried changing all the app ID entries to my own and then publishing the app, but then nothing is actually published (and no errors).

What is the correct procedure to make private changes to an existing cloud app? Thanks for any advice / steps.

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [August 5, 2022, 8:50pm UTC](https://community.homey.app/t/how-to-fork-a-local-cloud-app-nowadays/66973/2 "2022-08-05T20:50:57Z")

</div>

> [@Chris\_Brandhorst](#):
>
> OAuth2 CLIENT\_ID and SECRET are not set in an env.json file

You’ll have to get your own Client ID and secret of the device/app/service you want to use and put them in a `env.json` file (so it isn’t OAuth for the bridge/cloud).  
Further the development is the same on a Homey Pro, even if they support Homey (beta).

---

<div class="post-metadata">

**Author:** ![Chris\_Brandhorst](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chris_brandhorst/32/12449_2.png) [@Chris\_Brandhorst](https://community.homey.app/u/Chris_Brandhorst)\
**Post date:** [August 6, 2022, 6:43am UTC](https://community.homey.app/t/how-to-fork-a-local-cloud-app-nowadays/66973/3 "2022-08-06T06:43:54Z")

</div>

@Caseda Thanks for the quick response. I am unable to find how I should get that ID/secret, could you enlighten me?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [August 6, 2022, 7:01am UTC](https://community.homey.app/t/how-to-fork-a-local-cloud-app-nowadays/66973/4 "2022-08-06T07:01:39Z")

</div>

> [@Chris\_Brandhorst](#):
>
> I am unable to find how I should get that ID/secret, could you enlighten me?

The API that the app uses requires them, and will typically provide them (usually, by registering yourself as a developer).