Overview
The asset workflow involves:- Downloading or preparing your app build
- Uploading it to Limrun Asset Storage using
getOrUpload - Creating an instance
- Installing the app on the instance using the asset URL
Complete Example
This example downloads Expo Go and demonstrates the full asset workflow:How It Works
1. Asset Upload with MD5 Deduplication
ThegetOrUpload method automatically:
- Computes the MD5 hash of your file
- Checks if an asset with the same name and MD5 already exists
- Only uploads if the file doesn’t exist or has changed
2. Using initialAssets
You can also configure the instance to pre-install the app during creation:3. On-Demand Installation
Install apps after the instance is created:Benefits
Efficient Storage
Upload once, reuse across many instances
Fast Deployment
Skip upload time when creating new instances
Version Control
Manage multiple versions of your app as separate assets
Bandwidth Savings
MD5 deduplication prevents unnecessary uploads
Use Cases
- CI/CD Pipelines: Upload builds from your CI and install them on test instances
- Multi-Environment Testing: Test the same build across different device configurations
- Team Collaboration: Share builds via asset names without re-uploading
- Version Testing: Keep multiple versions in storage and switch between them
Next Steps
Asset Management
Learn more about asset management
iOS Instances
Explore iOS instance features