Dokploy UI navigation is network heavy

What problem will this feature address?

Unsure if it's a bug or something that requires improvements, I tried to find a related issue with no luck so please tell me if it does exist :)

It seems to use Tanstack Query (or similar auto-refetch logic) when navigating and refocusing window, and the payloads received are enormous.

The frontend app assets are correctly cached but I'm here referencing the payloads.

It seems to fetch everything the all nested pages require, at once, and multiple times through further navigation in the UI.

I only have a single project with a single application that contains a Docker Compose with 50 lines, and minimal domain & environments configurations.

Maybe having a payload is normal as of how the UI works and needs, but the issue is mostly the constant "refetch-all" which also can not be an issue because we always want fresh data ?

Overall when Dokploy is self hosted, it can consume our server out Traffic and generate costs.

Describe the solution you'd like

Optimize fetchs so Dokploy UI fetch smarter and consume less Network when refocusing window and doing subsequent navigations.

Describe alternatives you've considered

None, except being forced to use Dokploy Cloud to not have to monitor Network usage of the server hosting Dokploy Manager.

Additional context

No response

Will you send a PR to implement it?

Maybe, need help

Start by profiling the Dokploy UI in browser network tools while navigating nested pages and refocusing the window, comparing the repeated payloads described in the issue. Determine which fetches are repeated unnecessarily and define done as reducing redundant network traffic without making required data stale.