Is there a way to use a local zipline manifest while one from the network is downloaded in parallel (along with modules that were changed).
The use case - code push would be a good to have but want to avoid the network delays.
Yup, already using this, but when an update is pushed to the server zipline would first load the new manifest from the network and then would fetch any changed modules from the server right? Is there anyway we can use the cached manifest or the embedded manifest here while updates are downloaded async?