hub.json
and tests.json
) in a .runpod
directory to define metadata, hardware requirements, and test procedures. See the publishing guide to learn more.
4. Automated build pipeline: When a repository is submitted or updated, the Hub automatically scans, builds, and tests it to ensure it works correctly on RunPod’s infrastructure.
5. Continuous release monitoring: The system regularly checks for new releases in registered repositories and rebuilds them when updates are detected.
6. Deployment interface: Users can browse repos, customize parameters, and deploy them to RunPod infrastructure with minimal configuration.
Dockerfile
.
.runpod
directory, following the instructions in the Hub publishing guide.
2. Create a GitHub release to establish a versioned snapshot.
3. Submit your repository to the Hub through the Runpod console, where it will undergo automated building and testing.
4. The Runpod team will review your repo. After approval, your repo will appear in the Hub.
To learn more, see the Hub publishing guide.