You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering on which is the best way to upgrade a Production Live – Package Instance.
I previously read Modifying an Existing Package on the docs. The recommendation is to just fork the package and deploy it under another package handle.
This works fine for new users that use this new handle. My question is: How can I add some new functionality for a user that already is using an existing instance with personal data uploaded?
Is the recommendation to create a new instance of the Package 2.0, migrating all existing data to it, or is there another, more straight forward way?
For my specific case, every user has its own specific instance running, and I'm updating the package sometimes with new features. I was wondering how to make the existing users migrate and have the new things available.
Thanks 😁
The text was updated successfully, but these errors were encountered:
Hello!
I was wondering on which is the best way to upgrade a Production Live – Package Instance.
I previously read Modifying an Existing Package on the docs. The recommendation is to just fork the package and deploy it under another package handle.
This works fine for new users that use this new handle. My question is: How can I add some new functionality for a user that already is using an existing instance with personal data uploaded?
Is the recommendation to create a new instance of the Package 2.0, migrating all existing data to it, or is there another, more straight forward way?
For my specific case, every user has its own specific instance running, and I'm updating the package sometimes with new features. I was wondering how to make the existing users migrate and have the new things available.
Thanks 😁
The text was updated successfully, but these errors were encountered: