Just to clarify before I do this.
Add the built-in WC app first and then "Un-Match a Package" in HPM and remove the WC manifest?
Un-Match tells HPM to "forget" that it's managed by HPM. So.. doing the UnMatch before or after switching to built-in, won't matter. I'm not sure that it needs that however. Given WebCoRE is still a community app, then the developers MAY continue to use Github. This is a question for them. You can UnMatch then follow it by a Match cycle, a day or week later, to get it back if that's the desire.
Yes. I just replied to a newer thread which expalins the altered concept.
Just waiting on the update path going forward.
First, there is no reason to move to the built-in app if you already have the community app; they are essentially the same. Using the built-in app will, of course, save you the need to install or update webCoRE on the hub yourself. It sounds like you're using HPM, which should make this pretty easy. On the flip side, you'll no longer be able to update (or not) webCoRE separately from the platform, not that this should be a concern in most cases. Everything I've seen suggests that will continue to be open-source and maintained as before.
Note that you can have both apps installed at the same time if you want. I might give one a different name to make them easier to distinguish in the webCoRE Dashboard, but the Apps list on the hub will show you user vs. system apps, so you can always tell there. There is no automatic migration path, as it seems you've found in the other thread now, but the webCoRE Dashboard should let you move pistons from one to the other as long as you have both hubs registered there. So, if you choose to move, maybe you'll want to get the built-in one up and running before removing the community version — or not move at all — but either way should work.
I'm not sure that you really need to "unmatch" in HPM, though you could and then uninstall and remove webCoRE manually. Otherwise, shouldn't the regular "Uninstall" feature in HPM work here? And you definitely shouldn't need to remove a manifest unless you added a custom manifest instead of using the one HPM would have found on its own via the built-in means.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
