The basics


The Publishing spaces are used as naming spaces, i.e. as prefixes to the names of components. Each component in the Cloudsmith map is placed in a name-space reflecting where it was found.	Publishing spaces are used to distinguish unrelated components that have been given the same name (for example, "com.myorg.mycomponent" becomes "public.yourspace:com.myorg.mycomponent"). They also are used to manage content availability and publishing rights.

Creating spaces

When a Cloudsmith identity is created, both a public ("public.username") and private ("private.username") space is associated with that identity.

A second "temporary" private space is also created to hold artifacts created during execution of certain actions, such as "resolve & materialize." This temporary space is emptied at the end of each user session.

Signed-in users can create any number of additional private or public publishing spaces.

Deleting spaces


You can delete any space that you have created. You can not delete any of the three default spaces Cloudsmith generates when your account is created.	When you delete a space, both the space and the content in it are deleted. Deletion is permanent, and deleted content can not be restored.

Naming

Users can create spaces only within their respective name-spaces. (This is to prevent "name squatting" and similar abuses.) The following naming rules apply:

Spaces are prefixed with "public.username" or "private.username" by the system.
Only letters (a-z), digits and periods "." may be used
Names may not begin or end with a period
Adjacent periods ("..", etc.) may not be used

Cloudsmith does not support granting of "root" spaces, except where we have had the opportunity to the verify ownership of the domain. (This capability will be available in a later release.) We only support the public Cloudsmith space, and spaces corresponding to repositories that we have found.

Access

The contents of public spaces are available to all Cloudsmith users. The content of private spaces are available to the space's owner and those the owner invites to share the space. The only exceptions are the two default private spaces (permanent and temporary) associated with a user identity, which are "personal" to that user.

Sharing is role-based. Sharing can be "read only" (i.e. viewing and materializing), "read/write" (plus publishing) and full "admin" (plus space management, etc).

Cloudsmith is the "owner" of spaces not owned by an individual user (i.e. the name-spaces that are automatically generated when public repositories are mapped). This means that Cloudsmith can share those spaces, for example, with committers to "mapped" projects.

In order to publish into any publishing space (i.e. to publish at all), you must have a Cloudsmith identity. This allows you to publish into your own private and public spaces, as well as into any other private space to which the owner has shared publishing rights with you. (Note: in order to publish into a private space other than your own, the email address associated with your profile must have been verified.)

Spaces & Profiles

Each publishing space is also associated with a user profile of the owner. For example, consumers of configurations published into a publicly readable space would see that profile as the "publisher".

When a space is created, the owner's default profile is associated with the space. A different profile can be used by selecting the space, clicking on the profile image and selecting a new profile.

(Note: new profiles may not be immediately visible, due to the way the pages are cached. The new profile will show up with the next sign-in.) For more information, see profiles.