The basics


Users publish virtual configurations they have created to add them to Cloudsmith's map and share them with with other Cloudsmith users.	A configuration can include any content that can be found in the Cloudsmith map.

Publishing at Cloudsmith

When you publish a virtual configuration, metadata representing it is committed and linked in to the rest of the Cloudsmith component map. (Remember: Cloudsmith is not a code repository, so the actual artifacts implementing the configuration stay where they are.)

Once added to the map, your configuration can then be searched for, materialized, republished within a new configuration, just as any content within the map.

Note that you can delete a configuration once it has been published in a private space at Cloudsmith, but you should verify that it will not break any existing configurations. Configurations published to public spaces can not be deleted, since the impact of the deletion can be harder to determine. (A future release will allow configurations to be moved from one space to another, although not necessarily deleted.)

Publication routes


Cloudsmith provides a simple mechanism to create your distros online. The publishing capabilities on the site are supported by a publishing wizard.	The wizard lets you select the components and distros from the map that are required for your own distro, "stacking" them together into a larger configuration that you publish as a virtual distro.

Publication spaces

A publisher selects the publishing space used for publication from the list of spaces the publisher owns and those to which the publisher has been invited with write access by their respective owners.

Content published into a public space is available to all Cloudsmith users (including those not signed in). Content published into a private space is available only to those with whom that space has been shared.

For information on sharing, see sharing spaces.