Skip to main content
Pushing data involves uploading your local changes to the cloud. To view your local changes, click the Changes button in the left nav.

​
Pushing Content to a Workspace

You MUST have have a local directory mapped to a cloud workspace to push local versions to the cloud. If your workspace is cloud only, map the workspace first.
Every modification you make to file metadata, libraries, tags, and workspace details will be included in the push table. This table displays only the pushes related to the currently selected workspace.

​
Staging & Pushing Your Changes

On the Changes view, you will see a list of all local changes made by you. From here, you can select related changes in order to push them as a group with a push message title and optional description.
1

Select related changes

Choose the data you wish to push and stage it for a push by clicking the checkboxes on the items, then clicking the Stage changes button in the top right.
2

Describe your changes

Write a brief yet descriptive title to summarize the reason for your changes, with an optional more detailed description.
3

Upload your changes

Click the Push Changes button to send your changes to the cloud.
When you click the Push Changes button, Mudstack will fetch before the push to check for conflicts.
By default, only the current version of any file in the staged area gets pushed to the cloud. In most instances, this will also be your last save for the file unless you manually set an older local version to be the current version.

​
Unstaging Changes

At any point before clicking the Push Changes button, you can unstage changes to remove them from that push. To do this, simply check the items that you no longer want and click the Unstage changes button in the top right of the Staged Changes section.

​
Discarding Changes

You can discard a change by clicking the checkboxes on the items, then clicking the Discard changes button in the top right.

​
Uploading Non-current Versions

If you want to upload any non-current local versions for any reason, Mudstack allows you to do this from outside of the regular push flow described on this page. Go to a file in the Files view, go to the versions tab, and select Save version to cloud option on an older local version. This will automatically push that older version to the cloud.
See upload non current versions for more Info.

​
Automated Pushing

Some data will be pushed automatically. This will happen immediately after a change in order to maintain continuity with the cloud workspace. Automated pushes include:
  1. Account Data
  2. Workspace Deletion
  3. Workspace Creation -> Send to Cloud

​
Cloud Import

On occasions where you need to import large volumes of content to Mudstack on a one-off basis, we recommend using our Cloud Import feature. This allows you to upload folders to the root of your workspace without going through the staging process. This is much faster as it skips the local indexing and backing up process that is followed by the app when watching for changes and staging them for a push. To use this feature, go to Settings/Account/Workspaces, select your workspace from the dropdown and then use the Cloud Import section to upload your content.