fix(startup): posthog issue when enabled and no connectivity

[vijay-jangir]

Dockerfile enhancement, posthog bugfix

posthog doesn't let application start if there is any connection issue, temporarily fixed it to atleast get the application in started mode.
Updated dockerfile for ui and api so that it can run seemlessly on openshift update dockerfile for api for caching layers more efficiently

Closes #

📑 Description

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

[vercel]

@vijay-jangir is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (424d3d1) 68.04% compared to head (89f53b2) 68.07%.
Report is 1 commits behind head on main.

❗ Current head 89f53b2 differs from pull request most recent head 08aa3c8. Consider uploading reports for the commit 08aa3c8 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #631      +/-   ##
==========================================
+ Coverage   68.04%   68.07%   +0.03%     
==========================================
  Files          48       45       -3     
  Lines        2691     2390     -301     
==========================================
- Hits         1831     1627     -204     
+ Misses        860      763      -97     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[talboren]

@vijay-jangir I've edited the EventCaptureMiddleware to disable posthog completely unless otherwise configured since we're not really using it and the way you fixed it would've still caused the API to behave strange.

[talboren]

@vijay-jangir this now lgtm, lmk once you've had a chance to take a look and I can merge this in.

[talboren]

LGTM

[vijay-jangir]

This looks fine, as long as we're okay with posthog still crashing the backend if network is behind a proxy or firewall, incase the POSTHOG_ENABLE is set to true.

[talboren]

This looks fine, as long as we're okay with posthog still crashing the backend if network is behind a proxy or firewall, incase the POSTHOG_ENABLE is set to true.

It's now disabled by default, so it won't :)