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

Compare STAGING to Production content

Quick_Learner

Hi, I'm trying to find if there is a way to achieve the below. Kindly suggest.

Scenario: I have a branch "PROD" which is supposed to be in synch with production content (deployed to web servers). However, due to the way how workflows are developed, STAGING of PROD contains few files which do not match what is there out in Production (ex: I modified something in PROD branch directly and then submitted manually. Then I realized that this change is not required and so I just left the file as is)

Is there a way how I can identify which of the files in STAGING do not match my production web server? Once the differences are found, I'm planning to synch the STAGING accordingly and then create an Edition out of it. Then I can consider that Edition as my virtual initial Edition.

Please let me know if I did not describe this clearly. I will try to modify or provide more information.

Thanks,

Nagesh K

Find more posts tagged with

Comments

nipper

Best idea would be to write a deployment that does a comparison, (either date or checksum) between TS and Prod.

Do not run it per say, instead use the UI to run a SIMULATION. It should tell you what is different.

The other thing you can do, IF you have an OD base server installed on the production server, is to do a reverse deployment, from Prod to a new workarea on the TS server and then using a tool like beyond compare to compare the two.

Adam Stoller

To expand a bit on Nipper's response:

Best idea would be to write a deployment that does a comparison, (either date or checksum) between TS and Prod. Do not run it per say, instead use the UI to run a SIMULATION. It should tell you what is different.

You can run the deployment from the command line using the -sim flag to achieve the same results - you then have to look at the log file that is generated from the simulated deployment in order to determine what would have been deployed as the result of a comparison deployment.

The other thing you can do, IF you have an OD base server installed on the production server, is to do a reverse deployment, from Prod to a new workarea on the TS server and then using a tool like beyond compare to compare the two.

Nipper actually knows better - or knows how to phrase things better usually, as long as you have an OpenDeploy Base Server installed on the TeamSite server (standard practice) and an OpenDeploy Receiver (or Base Server) installed on the production web server - you can initiate a reverse-deployment from the Base Server to retrieve the files from the web server to a location of your choosing (that has been configured within OpenDeploy Base) on your TeamSite server and then use whatever tool you like (the recommendation for Beyond Compare is a good one IMO) to compare / contrast the files deployed against the files within TeamSite.

Quick_Learner

Thanks nipper and ghoti. I appreciate the responses. I will do the simulation and will get back in case of more questions.

Regards,

Nagesh K

Anil Kumar

Hi Nagesh,

We can have a submit task in the workflow at the end, with "Successful Prod Deployment" string as submit info.
suppose a file has 5 versions, in which 3rd version is created by workflow with the above submit info. Anytime you see versions with that info would be treated as a file actually present in webserver.

Tweak this a bit, to serve your purpose.

Regards, Aneel