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; } } }

Use Teamsite to manage another server content

System

We are looking for a way to use teamsite to manage content or application that are sitting on another server.

Here is what we want to achieve.
1. We want to utilize teatmsite workflow and opendeploy so that developers can deploy application to production.
2. We don't want to interfere the current development process, it means developers should not have to import the application into teamsite for deployment.
3. The idea solution will be Teamsite has a way to know the application that is sitting on another server, nfs mount is good solution but it means everything will be managed within teamsite
Any good suggestion?

Jason

Find more posts tagged with

Comments

Adam Stoller

OpenDeploy can deploy files from any [supported] system to any [supported] system with or without TeamSite being involved.

Workflow only interacts in and with assets in TeamSite.

You could, conceivably have a workflow with no files attached that executes an externaltask script using information provided during instantiation to kick off OpenDeploy - which if you have the remote repository mounted via NFS on the TeamSite server (not *in* TeamSite) would work..

What exactly would the workflow process be (other than the deployment)? Is there any real need for the workflow here if you're not using TeamSite to manage the application files?

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

2016-04-22 10_43_51-Database Administration Tool.png

Migrateduser

We want to use workflow as a production control process so that unix group doesn't have to copy the application manually from one server to another. My proposal is to have a workflow that should allow developers to attach files within Teamsite(The actual content is sitting on application srever) and they can setup a schedule deployment, however, this schedule deployment has to be authorized by Unix group. They also have option to roll back to previous edition in case there is any errors.

Jason

Adam Stoller

I'm not sure I understand all that you're doing - but it sounds like you're dealing with some files that *are* in TeamSite and some files that *are not* in TeamSite - yes?

Perhaps a cgitask script that would allow you to select files from the NFS mount point (*outside* TeamSite) which you could then stuff into job variables and then when you run the externaltask to perform the deployment (I'm assuming a filelist deployment) you could pull in not only the files attached to the job, but the files referenced in the job variables -- perhaps as two distinct filelists for two distinct sections of the deployment configuration file (or two distinct deployment configuration files).

Not sure it that helps - but hopefully it gives you some ideas to think about that might help you figure out a solution.

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