Skip to content

Publish to Remote

Overview

The Publish to Remote feature in CreativeHub allows users to synchronize their locally made changes with a different remote server. This functionality is essential for setups involving multiple CreativeHub servers, where content or configurations need to be shared or updated across servers.

Prerequisites

The user initiating the publish action must have proper credentials, which might involve: - Token-based authentication (e.g., OAuth) - API keys - Appropriate permissions and access rights to publish to a remote server

Version Labeling

When publishing commits, CreativeHub automatically manages version labels:

  • Latest: The most recent commit is automatically labeled as "Latest"
  • Production: Any commit can be manually marked set as a Production version during the publish process

How to Use Publish to Remote

  1. Log in to your CreativeHub application on the local server

  2. Navigate to the project and select the commit you want to publish

  3. Select the Publish to Remote option for the chosen commit

  4. Configure the publish settings:

  5. Choose the target remote server from the available list

  6. (Optional) Check the "Set as Production version" checkbox to mark this commit as the Production version

  7. Confirm the action to publish your changes

  8. Verify completion: Once the process is complete, you'll receive a notification confirming that the changes have been successfully published to the selected server

Use Case Scenarios

Collaboration Across Teams
Teams working on separate CreativeHub servers can share updated content or configurations seamlessly.

Backup and Disaster Recovery
Critical data can be synchronized with a backup server to ensure business continuity.

Multi-location Workflows
Enables smooth workflows when different locations or departments need access to shared content.

Version Management
Allows teams to maintain clear Production and development versions across multiple servers.

Important Considerations

Network Dependency
This process requires stable internet or intranet connectivity between the servers. Ensure network reliability before initiating large publish operations.

Error Handling
If the connection fails or there's an issue with the data, the system may retry automatically or log an error for manual review.

Scalability
The system supports multiple remote servers, with options to prioritize or batch changes for efficient synchronization.

Permission Validation
The system validates permissions before allowing publish operations. Ensure your account has the necessary rights for the target server.

Best Practices

  • Always verify you're publishing to the correct remote server
  • Use the Production version marker strategically for stable releases
  • Review commit changes before publishing to avoid propagating errors
  • Maintain documentation of which commits are marked as Production
  • Monitor network status before publishing large projects