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

Deleting Files from Production using workflows/ open deploy

System

Can I configure OpenDeploy to do a compare of "TeamSite" vs Production and delete files that are in production but not in TeamSite?

What is best THE praactice for deleting files from production using OpenDeploy?

Find more posts tagged with

Comments

vpatel

Can I configure OpenDeploy to do a compare of "TeamSite" vs Production and delete files that are in production but not in TeamSite?

Yes -- look at the Directory/TeamSite Comparison Deployments in OD guide. Keep in mind that this may take a while depending on how much content you are comparing and your network bandwidth.

CRB

just in case if you aren't doing this already, make sure you use it with teamsite EDITIONS. i have seen clients who only deployed from STAGING and never published any editions.

Migrateduser

Actually we are deploying from Staging.
The client will create Editions manually once a week, or for major deployments.
If you deploy from editions, wouldn’t you have to create a new edition for every push to production? There could be 20 editions created every day.

nipper

Actually we are deploying from Staging.
The client will create Editions manually once a week, or for major deployments.
If you deploy from editions, wouldn’t you have to create a new edition for every push to production? There could be 20 editions created every day.

Yes you would. There will be little to no increase indisk (though a big jump in i-nodes on unix). Many people do that with a lot more pushes daily.

CRB

Actually we are deploying from Staging.
The client will create Editions manually once a week, or for major deployments.
If you deploy from editions, wouldn’t you have to create a new edition for every push to production? There could be 20 editions created every day.

Edition can be published automatically thru the workflow.
yes you will have large number of editions, as Andy mentions, it will not increase your diskspace usage significantly. and it is a lot easier to recover/restore/revert your website using editions than going thru staging to figure out what files changed and what version of the file is good.