Date: Fri, 29 Mar 2024 01:46:00 +0000 (UTC) Message-ID: <1310021515.7377.1711676760850@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7376_309901118.1711676760847" ------=_Part_7376_309901118.1711676760847 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Maintenance of your Registry installation is an important part of ensuri= ng that you are getting the value and impact that you need from this import= ant tool. This page provides information about upgrading the Registry, mana= ging backups, and a few advanced use cases for more experienced users.
If you have previously installed COmanage Registry, follow the instructi= ons at "Upgrading Registry= ".
Backing up COmanage Registry is as straightforward as backing up the dat= abase that you are using. All configurations and data for your instance of = COmanage are stored within the database.
Incorporating features that haven't yet been released= p>
This approach is only advisable for teams with internal DevOps and techn= ical resources, and a strong familiarity with PHP, Github, and systems mana= gement. There is always a risk to using in-progress code in a production en= vironment, and doing so should only be considered when absolutely required.=
Although rare, there can be occasions when = institutions will find it necessary to incorporate a developed feature befo= re it is generally available in a released version of the Registry. In thes= e situations, it is possible to incorporate all or some of the work in the = working "Develop Branch" of the code repository where the development team = is committing their work.
If you are sure that your institution has t= his need, first re-read the warning box above, and then peruse the followin= g links for more information: