This repository has been archived by the owner on Dec 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Deployment
carlashley edited this page May 1, 2024
·
1 revision
Deploying Apple's audio content packages with this tool can be done one of several ways:
Each of these modes will require the tool to be run as root either via sudo (if manually running the tool), or through other means.
No specific method of deploying these packages is recommended, as each has pros/cons that may make it more/less appealing to use in any given environment.
- Pro: No need to use local resources to keep copies of the audio content packages.
- Con: Each deployment will "waste" bandwidth that other users on your network might find valuable.
- Pro: Only downloads audio content packages from Apple once (and only if they're not already on the Caching Server). This minimises bandwidth used.
- Con: Content stored in the Caching Server is removed after a certain period of time where it hasn't been accessed.
- Con: If a package requested by one client has not been downloaded into the Caching Server, and other clients request that same package simultaneously, a race condition is created and some clients may not install packages as they're only partially downloaded into the cached copy. Re-running this utility or allowing an audio app to install the apps would be required. To avoid this scenario, deploy the audio content packages to one Mac and then any remaining devices to allow the contents to be cached first.
- Pro: Only downloads audio content packages from Apple once. This minimises bandwidth used.
- Con: From time to time, Apple will update a package with a new version. This may require the local HTTP/HTTPS mirrored copies to be updated occasionally.