FROM DISCOVERY TO DEVELOPMENT
Open a project, connect its registry, and add bricks from the editor.
In Turian, open the Bricks panel, choose Project and open Registries. Enter this host with the package's namespace scope and the registry's trusted public key:
https://store.mass4.orgThe public MASS4 registry is already configured in Turian. A local store needs its own host and development trust key. Older clients that require a registry endpoint use this host followed by /v1/.
Return to the Bricks tab. Choose + → Add by name…, paste the package ID from its store page, and choose Add. Turian resolves dependencies and verifies signatures and archive integrity.
To select an exact version, use the dependency entry shown on the package page in Bricks/manifest.json. Obtain registry public keys from the administrator through a trusted channel.
Public packages on the public store need no token. For private packages or publishing, sign in through a compatible CLI or panel, or create a scoped token in publisher tools.
Authorization: Bearer YOUR_ACCESS_TOKEN
Keep tokens out of package manifests and source control. Use a separate token for publishing.
Manage publishing & access ↗Sign in with an authorized publisher account, prepare the package manifest and archive, then publish using the management page or HTTP API.
Published versions are immutable. Publish a new version to deliver a change; withdraw a release when it should no longer be installed.
Open publisher tools ↗Run the store with your own publisher permissions, visibility rules, accepted formats, and licenses. Public and private packages use the same API contracts.