Maybe I'm late to the game and didn't get the memo, so I gotta ask: Is HubConnect still an option for connection two hubs that don't reside on the same LAN?
Took my time reading whatever docs I could find, installed the Pro Bundles mentioned in the official guide, but came away with a few stumblers:
#1 How can you do OAuth if pro bundles won't open the app code?
#2 Where do you get the server ID that Remote needs to connect?
#3 Am I just wasting my time going down this rabbit hole? (All of the official threads and such appear to be closed now, leaving me to wonder if something big changed)
@csteele would be the current resident expert on the status of the app but last I heard it was still working.
NA, threads get closed after a period inactivity(or if people start fighting) and not necessarily an indication of the functionality being defunct.
1 Like
HubConnect is still functional. Bundles include the option of setting Oauth. I just installed the Remote Server Pro Bundle:
and it shows as Oauth Enabled:
You Install Server.zip on one of your hubs, which bundles Server & Server Instance.
You Install Remote.zip on all the rest of your hubs.
All hubs should get the UniversalDrivers.zip
At this point in the process, all the code is on the hubs, but none are available for use in Apps. On each hub, go to Apps and Add HubConnect.
On whatever hub you elected to be Server, create a remote and the Key is created after answering the questions.
On each Remote Hub, paste in the key and the connection is made.
If you get this far in creating the remote within Server:
click Refresh to get:
4 Likes
Okay, great, that gets me headed in the right direction and aligns with everything my tired eyes gleaned on rereading your online instructions. I think my dyslexia was kicking in at several points with all the similar-looking nomenclature.
Really appreciate the prod!
