The Push Publishing feature provides a way to “push” dotCMS objects (including but not limited to Content, File Assets, Folders, Hosts, Content Types, and Users) to another dotCMS server(s). Objects can be scheduled to be published or unpublished either in groups or individually during the editing process. You may also remove content from a publishing queue after it has been added.
There are two basic types of push endpoints that can be created under any push publishing environment, a static or a dynamic endpoint. Each of the push publishing documentation sections discusses the difference pushing to either static, dynamic, or both types of endpoints within the same environment. To understand the difference between static and dynamic publishing, please refer to the Static and Dynamic Publishing documentation.
Once an item has been added to the publishing queue, a bundle is created. This bundle can be pushed to a Publishing Environment (a group of other dotCMS servers or endpoints). This allows for the easy migration of content/objects between dotCMS instances.
The following videos provide an overview of Push Publishing configuration and the Push Publishing process, and the documentation below describes each of the remote publishing steps in greater detail.
Push Publishing Part One: Configuring Environments & Servers
Push Publishing Part Two: Pushing Content
- Dynamic and Static Publishing
- What to Know Before Push Publishing
- Push Publishing Best Practices
- Connecting Remote Servers
- Integrity Checker
- Push Publishing Content
- The Publishing Queue
- Publishing Status
- Push Publishing Dependencies
- Push Publishing Permissions
- Pushing from Content Search
- Push Publishing Workflow Actions
- Implementing Static Publishing
- Troubleshooting Push Publishing
- Push Publish Listeners Configuration