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

in open deploy

System

A customer wants to make sure it can do an emergency roll back of its production Web site if it is attacked by hackers. The customer wants to use OpenDeploy to re-deploy directly from TeamSite to perform the emergency rollback. It does not want to have to re-create or re-build any assets as part of this type of emergency rollback. The emergency rollback deployment must deploy exactly the same assets that were on the Web server before the attack.
To insure the above requirement is satisfied, which one of the following types of assets must be versioned in TeamSite?

Compressed asset
Deployed asset
content store asset
Image asset
Derived asset

Find more posts tagged with

Comments

Migrateduser

Hi,

If that is the case for emergency roll back, I suggest you make use of editions in your Teamsite. Editions make use of the latest versions available in STAGING area, without consuming space (just the versions are taken care of). After creating the editions, any changes in the files would be stored with a new version of the file on iw-store (editions remain ubaffected by the changes), just like the versions created in CVS. You can always publish the editions to rollback to the previous version.

Also, you can always make sure that you publish your work through editions regulary on a monthly basis or whichever suits you. Let us know if anything more is needed.

-Rahul.

Adam Stoller

Hi,

If that is the case for emergency roll back, I suggest you make use of editions in your Teamsite. Editions make use of the latest versions available in STAGING area, without consuming space (just the versions are taken care of). After creating the editions, any changes in the files would be stored with a new version of the file on iw-store (editions remain ubaffected by the changes), just like the versions created in CVS. You can always publish the editions to rollback to the previous version.

Also, you can always make sure that you publish your work through editions regulary on a monthly basis or whichever suits you. Let us know if anything more is needed.

-Rahul.

Another thing to be aware of - if you are creating editions and deploying from editions - then you want to make sure your deployment provides for dataDifferent="t", otherwise OD will only deploy files that are newer than those on the target system and you'll fail to overwrite the files that were hacked.

You probably also want to use doDeletes="t" - but be sure you have any/all filtering configured correctly so you don't wipe out things on the web servers that are [intentionally] *not* versioned in TeamSite (ideally, everything in your docroot and other deployed-to directories would be versioned in TeamSite so that you wouldn't have to worry about the filtering.