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

OpenDeploy: Forcing the source to overwrite the destination.

PeteOlsen

How do I force the source to overwrite the destination regardless of age or any other factor?

Thanks
Pete

Find more posts tagged with

Comments

Migrateduser

What if you were to run a DNR before deployment which removes all of the files beforehand?

Migrateduser

What if you were to run a DNR before deployment which removes all of the files beforehand?

If the deployment fails then script should handle to rollback the deleted files. Insted you can touch the files using touch command in unix to change the timestamp that will solve the issue. If the files are in the STAGING then you might not able to touch the files as they are READONLY.

Are you using filelist or comparision deployment to deploy the files to target.

PeteOlsen

I don't know what you mean by a DNR. I don't remove the files on the destination because it is a large number of files and I only want to deploy the deltas. I want the source to be definitive.

Adam Stoller

How do I force the source to overwrite the destination regardless of age or any other factor?

Thanks
Pete

You want to do a complete deployment every time without using a comparison?

Do a big filelist deployment then.

If you want to make sure that any date-difference (older or newer) gets deployed with a comparison deployment, enable dateDifferent in the deployment config file.

If there's something else that you're trying to do - please try to provide more detail about what - and if possible - why.