# Do you still need the manual "Connect" page?

**URL:** <https://community.datagerry.com/t/do-you-still-need-the-manual-connect-page/869>\
**Category:** Community Support\
**Created:** [August 5, 2026, 1:13pm UTC](https://community.datagerry.com/t/do-you-still-need-the-manual-connect-page/869 "2026-08-05T13:13:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![abdullah-khalid](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/abdullah-khalid/32/860_2.png) [@abdullah-khalid](https://community.datagerry.com/u/abdullah-khalid)\
**Post date:** [August 5, 2026, 1:13pm UTC](https://community.datagerry.com/t/do-you-still-need-the-manual-connect-page/869/1 "2026-08-05T13:13:30Z")

</div>

Hey DataGerry community,

With DataGerry 3.2.0, we introduced `app-config.json` - a config file where you can set the frontend-to-backend connection (`protocol`, `apiUrl`, `apiPort`) ahead of time.

We still keep the old manual **Connect** screen (`/connect`) as a fallback — it lets a user enter host/port/protocol directly in the browser, saved to local storage, if the frontend can’t auto-connect.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/datagerry/original/1X/bf53a9345ee6c8fe898eed5b2fc06fb921ed216e.png)

**Question for the community: do you still need/use this manual connect screen, or does `app-config.json` cover your setup needs now?** We’re trying to decide whether to keep, simplify, or eventually retire it.

**Sincerly,**

Your DataGerry Team