publish triggers
Hello,
We have a multi-tier web environment and our web admins will only allow us to publish from Cascade to our development environment, but not directly to QA or production. Because of this, setting up a destination to QA or prod is not possible.
Is there any way to set something up in the CMS so that once assets have been published out to our dev server, there could be some sort of trigger to copy the files to QA and then to prod? Could a publish trigger hit some sort of web service to take care of this process?
What are the options for accomplishing this? Also, do you have to have a publish trigger within a workflow?
Thanks in advance for your help!
~Casey
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Tim on 01 Sep, 2010 09:00 PM
Hi Casey,
Yes, I believe you should be able to write a publish trigger to do something like this. For more information on publish triggers, check out the documentation located here.
Also, while the name is identical, publish triggers in workflows are completely different from publish triggers. So, you do not need to have a workflow set up for the type of publish trigger you will be considering.
Let us know if you have further questions!
Tim closed this discussion on 21 Sep, 2010 05:34 PM.