nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Opnedeploy running continously

System

Is it possible to have Opendeploy run a deployment continously - thus I've been asked to use Opendeploy so that if a user puts a file in a directory - Opendeploy would then fire off and deploy the content to the proper servers- I think what I've been asked is similiar to the robo-copy program? Any suggestions would be helpful

Find more posts tagged with

Comments

Hemant

I think you can use an event trigger to do the deployment.

Migrateduser

One of the things about the trigger-based approach is that something may arrive in the source directory while a previous deployment is already running. Another consideration is what to do with the source file after it's been deployed.

As an alternate approach, you could run a recurring scheduled deployment on a frequent basis. Of course, you still have to consider a deployment could take longer to run than the recurrence interval, resulting in the next deployment starting before the previous one completed.

There's an open feature request (#37349) for OpenDeploy to provide "hot folder" support out-of-the-box.

Cheers,

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Adam Stoller

Create a daemon service script to poll the directory from which you want to deploy files. When it finds files in there, have it kick off the deployment and wait for it to complete before deleting the files it just deployed (or see idea below) and polling the directory again.

If you're dealing with large files that might take a while (> 5 microseconds?) to write out completely, you may want to have the script create a list of file files and their timestamps - and only deploy those files whose timestamps are at least 1 second (perhaps longer) old.

The concept of keeping your own tracking file to record which files you've sent and which are ready to be sent can help to make the process more robust and less prone to problems like re-deploying the same file and/or deploying a partial file that's in the process of being written out.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Bowker

Todd,

You wrote: <b>There's an open feature request (#37349) for OpenDeploy to provide "hot folder" support out-of-the-box.</b>

Can you be a little more specific as to what this would do?

We have a couple of folders that are written to by an external process. When the file "ALLDONE.TXT" is updated, an iwat trigger recognizes the directory and pushed it out as desired.

Dan Bowker
Northern Trust
Web Publishing Technology

week_modifier.fcn

Migrateduser

The feature is not committed at this time, but here's a summary of the request:

Provide a way to automatically trigger a deployment when content hits some directory (a "hot folder"). The file may arrive by someone dragging-and-dropping to a shared folder, or via FTP, or some other means. The alternative is to write a custom script around a directory monitoring utility that kicks off deployments when new files arrive.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com