Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Note

Upgrading? Please visit the page Upgrading Registry.


Info

Information on installation using containers (e.g. Docker) is available here.

Installation Steps

  1. PHP
  2. Web Server
  3. Download and Install Source
  4. Database
  5. Email
  6. Registry Setup Script
  7. Cron
  8. Testing
  9. Setting Up Your First CO

  10. QA and Production Tiers
  11. High availability (HA) considerations

Troubleshooting

  • The directory registry-source/ contains a .htaccess with necessary mod_rewrite directives. Not all Apache configurations by default allow configuration options within .htaccess files. Be sure that your Apache configuration has the necessary AllowOveride configuration to allow that .htaccess file to be processed (this is not the default on Debian Squeeze and other Linux distributions).
  • Following an upgrade, failure to login due to Auth.User.name doesn't exist may be due to caches that need to be cleared.
  • Messages like Warning (2): preg_match(): Compilation failed: unknown option bit(s) set at offset -1 [CORE/Cake/Utility/Validation.php, line 782] are indicative of a bad version of PCRE, described above

Gears Components

While the architecture of COmanage Gears describes three separate components of COordinate (the backend system), COnsole (the web UI), and the REST COnnectors (for XML and JSON data transfers), the actual implementation is based on an MVC framework called CakePHP. As such, the technical implementation consists of one package, where the boundaries separating these three components is somewhat fuzzy. Roughly speaking, COnsole can be thought of as the HTML views and the REST COnnectors can be thought of as the XML and JSON views. While not strictly correct, this conceptualization is adequate for installation.

Prerequisites

...

  • .