Before you begin
- Complete set up a workspace and answer Yes when asked whether you have an existing SOCK.
- Prepare the existing SOCK
docs/folder you intend to publish. - Confirm you are working in the correct workspace with workspace admin access.
The three stages
| Stage | What you do |
|---|---|
| Choose folder | Pick the legacy SOCK docs/ folder |
| Preview | Check exactly what will ship and what will be replaced |
| Release & publish | Give it a version label and publish it to the workspace |
Choose the folder
- 01
Open the import
Continue from workspace setup, or open the import action for the configured workspace.
- 02
Choose the docs folder
Select the existing SOCK
docs/folder. MSOCK shows what will ship before writing anything.
Preview and confirm the replacement
Review the source folder, the file count, and the complete folder tree. Check what survives and what is replaced. When the preview is correct, choose Replace knowledge and continue.
Label and publish
- 01
Enter a release label
Provide the version label teammates will see, for example
26.0.0.0. MSOCK does not invent one for you, and nothing is published until you supply it. - 02
Publish SOCK
MSOCK copies the files into place, builds the bundle, uploads it to the platform, and finalises the distribution. Each phase is reported as it happens.
Verify the active distribution
Open the workspace Distribution tab and confirm the published SOCK is marked Active, with the expected version, stage, creation date, and publisher.
If publishing fails
| Problem | What to check |
|---|---|
| The folder is rejected | It must be a SOCK docs/ folder for this workspace |
| Publishing stops part-way | Nothing partial is served; retry from the import action |
| No version label accepted | A label is required — MSOCK will not choose one |
| The distribution is not Active | Reload the Distribution tab; if it persists, retry the publish |