ayo ayo - got a lil issue that I want to throw out for the team
We’ve been going through the growing pains of moving all of our servers / machines to a DaaS system with IronOrbit and I was giving speckle 2 a try today with my VD when I encountered an issue with the installation process, specifically an issue with local appdata.
Our VD structure routes all roaming data into a directory that is accessible to each machine the user is assigned to. However, it doesn’t change anything that would be placed in local / locallow and keeps those directories on the disk associated with that VD.
Here is the path for a typical machine
Now the path using our VD machine
I used the speckle manager to install everything and was able to link my account, but when I tried throwing a grasshopper component down a bunch of flags were raised around not having access to the right database. It seems like the gh connector (which I believe is in roaming) is searching for a database / cache, I believe it’s
AppData\Local\SpeckleSettings, but can’t find it since it’s located on the disk space of a VD machine while the connectors are being stored on the actual VD system structure.
We’ve experienced this same issue with other software and we’ve been putting together some solutions for re-routing some of the files and shortcuts during their installation process. I was figuring we could do the same, but I wasn’t sure what exactly would need to be re-routed or if changing the location of the database would cause speckle to break So, I guess my request for halp is will modifying the locations of local app data cause an explosion of some sort?