Registry
When you run bulker activate, it fetches the manifest from a registry if not already cached. You can also load from a local file.
Linking to a registry
Section titled “Linking to a registry”Set the registry_url in your config:
bulker config set registry_url=https://hub.bulker.ioOr edit the config file directly:
registry_url: https://hub.bulker.ioThe default registry
Section titled “The default registry”The default registry is hub.bulker.io, backed by a GitHub repository served via GitHub Pages.
Contributing a manifest
Section titled “Contributing a manifest”- Write a manifest YAML file (see Write a Manifest).
- Fork or clone the hub.bulker.io repo.
- Add your manifest under your namespace folder.
- Name it
manifestname.yaml(default tag) ormanifestname_tag.yaml(versioned). - Open a pull request.
After merge, activate with: bulker activate namespace/manifestname:tag.
File naming convention:
- Default tag:
namespace/crate_name.yaml - Versioned tag:
namespace/crate_name_1.0.yaml
Building your own registry
Section titled “Building your own registry”Set up your own registry using any file server with manifests organized by namespace. A GitHub repository served via GitHub Pages works well.
Structure your files as subfolders for namespaces, with filenames as {manifest}_{tag}.yaml. Then point your config to the new registry:
bulker config set registry_url=https://your-registry.example.com