Publish Queue Manager
An essential component of any large scale Movable Type installation is "Publish Queue." Publish Queue is a system by which files published by Movable Type are published in the background at the next available moment, as opposed to slowing down the commenting system and application as MT publishes lower priority files.
For the longest time, the Publish Queue was a black box. Users had absolutely no idea what it was doing and how many files were in it awaiting publication. This made diagnostics very difficult, if not virtually impossible.
Well, no longer. Publish Queue Manager provides the administrative console you need to better manage your queue.
Ashish Nagpal
December 11, 2008 9:55 AM | Reply
Hi Byrne,
I am trying to expand my system configuration by adding Publisher Machine which will be responsible only for executing Publish Queue via cron job. I want this machine to have READ ONLY Database (Slave) which will help me in improving the performance.
To implement this architecture I need to know:
When I publish a template via PUBLISH QUEUE - How does MT knows that there is template to be published via Q ? Is there a flag set in DB Table ? Where is the Queue status stored within MT ?
Because if the Q status is stored in DB and needs an update when its published, I will not be able to keep in READ ONLY.
Thanks, Ashish
Travis Spencer
December 14, 2008 9:48 PM | Reply
Ashish,
Your idea to access the MT DB read-only from the publisher machine isn't going to work because, as you suspected, that is where the queue resides. The info about the jobs, errors, and others state is in there, and it needs to be updated by the queue's readers and writers. The actual tables that hold the data are mtts* (ts as in TheSchwartz).
rdouthit
May 8, 2009 2:50 PM | Reply
Looks like a useful plugin. I have it installed and it's in the maintenance menu, but it has yet to show anything other than: "No jobs could be found."
I have most of my templates set for "publish queue" so this is curious. Suggestions anyone?