Distribution - How to setup scheduled publishing

We now offer automated scheduled publishing for editions and individual articles.

To enable this feature you need to contact support@pugpig.com with details of when you want editions to be published either regularly or ad-hoc / at one off times to cover when editorial staff are on holiday for example. A member of the Pugpig team will then set this up for you.

For scheduled publishing to work you will need to 'publish' the edition or article first and it is important to ensure before you publish that you have set the published date set to be (just before) the scheduled update date in the future.

If you are a member of the Pugpig team and need internal details on how to setup scheduled publishing for a customer details provided below:

--------

1. Configure scheduled flags in the database at the same level as OPDS endpoint config block e.g:
   
   'addon_type' => 'opds_endpoint',
       'name' => 'Content Feed',
       'schedule' => [
           'update_content' => [
              'minutesInterval' => 30
            ]
        ],
      ....
   
   Note: there are various options for the schedule, but for this case a generic ‘cron’ style is probably best. You can edit one online using http://www.corntab.com/pages/crontab-gui or http://crontab.guru/ e.g.
   
   So, for midnight Tuesday (Wednesday morning), you could use
   
   'schedule' => [
      'update_content' => [
         'cron' => '0 0 * * 3',
         ]
    ],
   
   
2. Add the 'supports_scheduled_publishing' => true, flag inside the OPDS endpoint level config block
   
3. At origin in the customer's CMS - the edition in the CMS must be set to published and the published date set to (just before) the scheduled update date. In fact, to make sure there are no problems with timezones, summer time etc, we'd advise setting the edition to be published at midnight the night before e.g Tuesday and set the cron to be 2 hours later (e.g 2am Wednesday), say.

​*But be careful to configure 'supports_scheduled_publishing' on the prod environment before setting editions to be published in the future, or else we will just make it visible there and then.*​ (edited)