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

How to backup previous files on OpenDeploy receiver side

EdwardXu

I am new for OpenDeploy.

Basically, I would like to backup previous files on OpenDeploy receiver side before the files are overwritten by deployment.

So after deployment on OpenDeploy receiver side, each file have two copies: one is new version, another is old version, such as .bak.

Any idea? Many thanks.

Find more posts tagged with

Comments

ISCBorisB

I am new for OpenDeploy.

Basically, I would like to backup previous files on OpenDeploy receiver side before the files are overwritten by deployment.

So after deployment on OpenDeploy receiver side, each file have two copies: one is new version, another is old version, such as .bak.

Any idea? Many thanks.

OTB Deploy does not have anything of the sort. You will have to code for it.

- You can use some flavor of so called "Deploy and Run" mode, DNR for short. In the simple case you can run your processes "On Target, Before" creating
actual or potential back-up candidates. In more elaborated scenarios you may parse deployment manifest to get a list of Files about to be modified and
create a back-up copies only for those. You may need two Deployments to do this sort of things, first one in "dontDo" Mode. [thread=37901]This thread[/thread] has some discussion
on similar topic.

- Another option, (in my opinion much better one) is to maintain Files' history on the source rather than Target. For example, if your Target is in TS store
you can simply publish an Edition right before Deployment and deploy from this Edition. With this scenario all versioning is automatic, your roll-back
copy is simply your previous Edition.

nipper

I am new for OpenDeploy.

Basically, I would like to backup previous files on OpenDeploy receiver side before the files are overwritten by deployment.

So after deployment on OpenDeploy receiver side, each file have two copies: one is new version, another is old version, such as .bak.

Any idea? Many thanks.

You do realize that TeamSite is a version control tool (among other things) and OpenDeploy is a software distribution tool. Might it be better to use the right tool for the right job ?

EdwardXu

Thanks for reply.

Actually, the presentation layer uses the files on receiver side. The presentation layer wants to know the different between new and old version ( current and the last). But the presentation layer does not have access to Teamsite.

nipper

Thanks for reply.

Actually, the presentation layer uses the files on receiver side. The presentation layer wants to know the different between new and old version ( current and the last). But the presentation layer does not have access to Teamsite.

OK, so Bo's idea will work, though it will be unwieldy. Do you do it for CSS ? Images ? JS ? Your DNR script will get ugly quickly.

If you want a complete backup, then I might do something like this:

Submit Changes -> Cut an Edition -> Deploy Edition to doc root 1 -> Deploy Previous Edition to doc root 2

ISCBorisB

The presentation layer wants to know the different between new and old version...

Even in this (admittedly hmmm... unusual) case it is IMO better to do from source. In line with my second proposal,
you can perhaps deploy current Edition + the previous one to some place that IS accessible to your front end.

With little ingenuity you will not even have to Deploy twice, just copy (or move, or rename - details)
folders/files before Deployment of the latest changes.