Pushing Sites and Folders

Last Updated: Nov 9, 2021
documentation for the dotCMS Content Management System

Sites and Folders can be Push Published and added to a Bundle from the Site Browser.

Right click on a Site or Folder to access the Push Publish and Add To Bundle options.

The Push Publish option only displays when there is at least one Receiving server defined in the Push Publishing configuration.

Access the Push Publish or Add to Bundle


When Folders are pushed the Bundle will also push:

  • The Site (an item of the Host Content Type)
  • Content located INSIDE the folder (Assets, Page Content, Links)
  • Content types of Content located in the folder
  • Subfolders

Exceptions: Files/objects referenced from WYSIWYG, Widget code, or parsed .vtl file will not be detected. These objects must be included in the push or the links will fail. In the case of Static Endpoints push publishing is comparable to FTP transfers - if the referenced files are not included in the push, the links will fail.

When Sites/Hosts are pushed the Bundle will also push:

  • All fields of the Site (including the Aliases field).
  • Host Content Types
  • Parent Folders and subfolders
  • Content
  • Content Types of the pushed Content
  • Html Pages
  • Links

For more information on how dependencies are handled, please see the Push Publishing Dependencies documentation.

Host Aliases

Sites are content, and each Site is an instance of the Host Content Type. When a Site is pushed, all fields of the content item, including the Aliases field, are pushed, and will overwrite the fields of the Site on the receiving server.

This means that you can not have different aliases for a Site on the sending and receiving servers. To access the same Site from different site or domain names on the sending and receing servers:

  1. Add the aliases for the Site on both servers to the Site on the sending/authoring server, and then push the Site to the receiving server (so both aliases will exist for the Site on both servers).
  2. Configure the DNS entries for all of the aliases to only point to the IP address of the sending server OR receiving server, as appropriate.


  • When pushing a folder, a case-insensitive comparison is made to existing folders on the receiving server.
    • If a folder exists on the receiving server with the same name but different case, the folder will be overwritten with the folder name (including the case) from the sending server.
  • Full Site pushes are especially recommended as a best practice when pushing to a Static Push Publishing Endpoint.
    • This ensures that no files or objects are missed due to dynamic dependencies, so all pages and objects on the static site will be rendered properly.

On this page


We Dig Feedback

Selected excerpt: