push publishing power. session scope what is dotcms push publishing how to set it up how it works...

PUSH PUBLISHING POWER

Session Scope

• What is dotCMS Push Publishing

• How to set it up

• How it works & what can go wrong

• How to troubleshoot

The Push Publishing Advantage

Allows webmasters & content publishers to completely deploy one or many dotCMS objects, using a single action, after the new content/site features have been fully tested and approved.

Documentation: WhatToKnowBeforePushPublishing

Vocabulary Changes for 3.0

The names of these objects have changed:

• Structures are now Content Types

• Hosts are now Sites

Authoring Server Setup

• Development (Authoring Server)

• Staging (Tests push from Development)

• Production (Minimal users and roles)

Push Publishing Configuration

• Same dotCMS versions between servers

• Set up sender environment and server(s)

• Set up receiver environment and server(s)

• Make sure both have same secure password

Dependency Support

Needed dependencies are pushed with dotCMS objects. Here’s some examples:

• Pushing a page (content, content type, folders, template, containers, etc.)

• Pushing a site takes every “pushable” dependency

What Can Be Pushed?

• Content, File, Form Types

• Workflow Schemes (with

Content Types)

• Content (multi-lingual)

• Tags (from content)

• Files, Forms, Widgets

• OSGI Plugins

• Pages

• Sites (Hosts)

• Folders

• Menu Links

• Templates

• Containers

• Users

What “Kinda” Pushes

• Categories “synchronize” instead of Pushing – there is no single category push

• Tags are pushed with content

• *Users push in group (*Caution!)

What CAN’T Be Pushed?

• Vanity URL’s (maybe later?)

• Roles & Permissions (hopefully never!!!)

“…Let Me Count the Ways”

• Manual Push Publish

• Push Publishing via Workflow

• Bundle it (… just a little bit )

Fixing Push Publish Mistakes

Corrections can be made by the following methods:

• Edit and push again

• Push to Delete- removes content from receiver

Users & Permissions

These recommendations are NOT written in stone

• Permission users & roles on auth server/staging only

• Do NOT duplicate users & roles on production

• Receiving server objects inherit needed roles from parent

• Inculcate a “Push-to-Production” politic

Troubleshooting

• From Push Publish Results Queue

• The dotCMS log (maintenance)

• The Integrity Checker

DEMO IN 3.0

Thing To Remember?

• One authoring environment for CP’s

• Avoid CP users & roles on production

• Check integrity between servers

• Integrate push publishing into workflow

• Test limited user push before hand-off

THANK YOU!