Up to now server, client and even CAD version had to be the same when performing updates.
Now
CADENAS_APPSERVER=https://appserver.domain.local?remoteSetup=0
as default allows for a complete PARTsolutions installation with updated
interfaces and still use the Appserver completely without any unc shares and
still have any modifications.[76]
CADENAS_APPSERVER (URL with parameters)
CADENAS_APPSERVER=https://<servername.domain>?<param1>=<value1>&<param2>=<value2>...
The following parameters are possible: (name,default value if not specified, meaning)
proxyAddr= => if specified, proxy address to use if noproxy=0
remoteFileSystem=1 => mount CADENAS_DATA via rfs from server
remoteSetup=0 (Default) => local CADENAS_SETUP | 1 => mount CADENAS_SETUP via rfs from server
remoteSiteSetup=1 => mount CADENAS_SITESETUP via rfs from server
remoteProgHelp=1 => mount CADENAS_PROGHELP via rfs from server
remotepool=1 => mount $CADENAS_DATA/pool and $CADENAS_DATA/shared from appserver (if =0, they are placed in the local data directory)
writeable=1 => mount rfs in writable mode and let the server determine if writing is allowed... (if =0, all mounts are readonly...)
inethelp=0 => use locally installed help in $CADENAS_PROGHELP (either local or per mount via appserver), if =1, mount CADENAS_PROGHELP from webapi.partcommunity.com
httpCacheSize=5000 => size of the rfs cache in Mb ... default is a max of 5GB in $CADENAS_USER/rfs