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
FYI, here's info on how to use the caching server with mist-cli
Currently (outside of super) we use something like this with a hard coded caching server address to determine wether or not to call mist-cli with the caching option, as it will fail if it is called with a caching server that is unreachable
ping -c 1 $cachingserver
reachable=$?
if [ $reachable == "0" ]
then
echo "caching server is reachable"
jamf policy -event sequoia-caching-server
else
echo "caching server is unreachable"
jamf policy -event sequoia-no-caching
fi
If parsing the output from assetcachelocator, that data might be under .results."current user"."saved servers"."shared caching"[] then .healthy, .hostport, and .rank to help determine the best choice
By using assetcachelocatorutil you can verify if a content cache is available and reachable.
in the Braindate at JNUC, it was mentioned that Mist CLI can utilize Content caching with a flag
-Brent David
The text was updated successfully, but these errors were encountered: