Custom client overwritten by newly-released version (updated UI design) #4162
Unanswered
benvium
asked this question in
Hubs Cloud Questions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have an instance of Hubs Cloud deployed onto DigitalOcean using the DigitalOcean MarketPlace package.
In addition have a custom client with code changes to enable user integration with another one of our systems.
This was deployed according to the instructions at https://hubs.mozilla.com/docs/hubs-cloud-custom-clients.html.
This morning, we noticed our integration had stopped working, and when we logged in we found the latest version of the client with the new UI was now on our server. Of course our changes were no longer in this version hence why the integration failed.
According to this discussion #4092, if we have a custom client deployed this should prevent the 'auto-updates' from applying.
Is there something we can do to prevent hubs client updates being pushed and overwriting our changes?
Of course we can just push our custom client again, but it'd be great to know it's not going to be overwritten again some time again in the future.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions