Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Help ! Looking for cron job to deploy files from S
DJL
Hi ! Very new to TeamSite & Unix . . .
We are looking to deploy files without using a
workflow as the user will submit to STAGING &
we would like a job to run a couple of times a day
& pick up anything new to STAGING . . .
Would ALL the STAGING areas on the server
need to be interrogated ? Or does will OpenDeploy
only pick up what has been updated ? Would it
only be a matter of running an OD script against
every STAGING ? Does anyone do this now ?
I hope this note makes sense . . .
Really looking for starting point to begin this
process . . . Any help would be greatly appreciated . . .
Find more posts tagged with
Comments
Migrateduser
OpenDeploy is capable of deploying only files that differ from source to target. FWIW: rather than deploying at a preset Time-of-Day, as 'cron' would do, I recommend deployment on an event. ToD means that no matter what state the source area is in, it gets deployed. By deploying on an event you can make the event depend on a consistent, usable state for the source content.
A good example of an event would be publication. This has two primary advantages: it ensures that your deployed content is retrievable by edition name; it requires a deliberate decision so that any criteria for making the decision can be inserted as these criteria are identified. The advantage of a named edition for each deployed set of content is evident: you can always revert to a known-good set of content. The advantage of the deliberate decision is that you'll find it easy to add tests around publication based on the worthiness of the content. Even if you start out with the criteria being "It's 2AM", eventually you may apply more sophisticated criteria as prerequisites to publication.
nipper
GO TO TRAINING
That being said, it is really hard to answer your questions cause you do not give enought detail. OD has a scheduler, so you can easily have it grab 1 or mor Staging Areas and ship them out. OD is very configurable, it can take everything, it can compare teh dates. If you use workflow, you can pass it a file list. You can also create editions and then ship out the TS differences (more efficient than date different).
How many branches do you have ? What are their purposes ? OD will only grab from 1 area and send it out, but if you have multiple branchs that need to be deployed that is easy.
So your stating point GET TRAINED.
Andy