|
|
|
@ -1,4 +1,4 @@ |
|
|
|
PACKAGER'S README FOR OMERO-5.0.8 |
|
|
|
PACKAGER'S README FOR OMERO-5.1.0 |
|
|
|
|
|
|
|
Damien Goutte-Gattat <dgouttegattat@incenp.org> |
|
|
|
|
|
|
|
@ -8,7 +8,7 @@ |
|
|
|
This file does not come from the OMERO project and the OMERO |
|
|
|
developers don't endorse anything of it. Official documentation and |
|
|
|
instructions for installing and running OMERO server should be looked |
|
|
|
for at <http://www.openmicroscopy.org/site/support/omeror5/sysadmins/>. |
|
|
|
for at <http://www.openmicroscopy.org/site/support/omero5/sysadmins/>. |
|
|
|
|
|
|
|
|
|
|
|
2. SYSTEM USERS AND GROUPS |
|
|
|
@ -55,20 +55,6 @@ |
|
|
|
The data repository is defined by the key `omero.data.dir' in the |
|
|
|
OMERO configuration. |
|
|
|
|
|
|
|
Note that OMERO 5.0.0 needs another directory, defined by the key |
|
|
|
`omero.managed.dir'. In the default configuration file, this key |
|
|
|
uses the value of the `omero.data.dir' key as follows: |
|
|
|
|
|
|
|
omero.data.dir=/OMERO/ |
|
|
|
omero.managed.dir=${omero.data.dir}/ManagedRepository |
|
|
|
|
|
|
|
but OMERO then complains that `omero.data.dir' is undefined, so you |
|
|
|
should really specify a full path for `omero.managed.dir`, even if |
|
|
|
the directory is located below `omero.data.dir`: |
|
|
|
|
|
|
|
omero.data.dir=/OMERO/ |
|
|
|
omero.managed.dir=/OMERO/ManagedRepository |
|
|
|
|
|
|
|
|
|
|
|
4. OMERO CONFIGURATION AND CONTROL |
|
|
|
|
|
|
|
@ -124,53 +110,13 @@ |
|
|
|
Then, you need to install and configure the Apache HTTP server to |
|
|
|
actually serve the application. |
|
|
|
|
|
|
|
NOTE: Do *not* follow the official OMERO documentation from this |
|
|
|
point, as it does not support running OMERO.web with Apache 2.4 and |
|
|
|
the mod_proxy_fcgi module. In particular, the configuration lines |
|
|
|
produced by the following command: |
|
|
|
|
|
|
|
omero web config apache |
|
|
|
|
|
|
|
are not suitable for Apache 2.4. |
|
|
|
|
|
|
|
Instead, add the following stanza to your Apache configuration: |
|
|
|
|
|
|
|
---8<---------------------------------------------------------------- |
|
|
|
RewriteEngine On |
|
|
|
RewriteRule ^/?$ /omero/ [R] |
|
|
|
|
|
|
|
ProxyPass /webclient fcgi://localhost:4080 |
|
|
|
ProxyPass /webadmin fcgi://localhost:4080 |
|
|
|
|
|
|
|
Alias /static /opt/omero/lib/python/omeroweb/static |
|
|
|
|
|
|
|
<Directory "/opt/omero/lib/python/omeroweb/static"> |
|
|
|
Options -Indexes +FollowSymLinks |
|
|
|
Require all granted |
|
|
|
</Directory> |
|
|
|
--->8---------------------------------------------------------------- |
|
|
|
|
|
|
|
(Make sure the mod_rewrite, mod_proxy and mod_proxy_fcgi modules are |
|
|
|
loaded. This is normally done in the default httpd configuration file |
|
|
|
provided by Slackware.) |
|
|
|
The following command will produce a configuration snippet that can |
|
|
|
directly inserted into the configuration file of Apache httpd: |
|
|
|
|
|
|
|
Start the web server. OMERO.web should now be reachable at |
|
|
|
<http://<hostname>/webclient> (for the main client interface) and at |
|
|
|
<http://<hostname>/webadmin> (for the administration interface). |
|
|
|
omero web config apache-fcgi |
|
|
|
|
|
|
|
Note that the OMERO web application does not seem to support being |
|
|
|
published at any other place than the server root ("/"). If your |
|
|
|
httpd server has another purposes beyong OMERO.web, you may want |
|
|
|
to use a VirtualHost; in that case, include the OMERO.web |
|
|
|
configuration inside a <VirtualHost> directive as follows: |
|
|
|
|
|
|
|
---8<---------------------------------------------------------------- |
|
|
|
<VirtualHost server_ip:80> |
|
|
|
ServerName server.hostname |
|
|
|
|
|
|
|
...insert the above-mentioned configuration stanza... |
|
|
|
</VirtualHost> |
|
|
|
--->8---------------------------------------------------------------- |
|
|
|
Start the web server. OMERO.web should now be reachable at the root |
|
|
|
of the web server. |
|
|
|
|
|
|
|
|
|
|
|
6. BACKUP AND RESTORE |
|
|
|
@ -198,7 +144,7 @@ |
|
|
|
|
|
|
|
http://www.openmicroscopy.org/site/support/omero5/sysadmins/server-upgrade.html |
|
|
|
|
|
|
|
To upgrade OMERO 4.4.x to OMERO-5.0.x: |
|
|
|
To upgrade OMERO 5.0.x to OMERO-5.1.x: |
|
|
|
|
|
|
|
- stop OMERO if it is running; |
|
|
|
|
|
|
|
@ -209,7 +155,7 @@ |
|
|
|
- upgrade the database: |
|
|
|
|
|
|
|
$ cd /opt/omero |
|
|
|
$ psql -h localhost -U omero omero < sql/psql/OMERO5.0__0/OMERO4.4__0.sql |
|
|
|
$ psql -h localhost -U omero omero < sql/psql/OMERO5.1__1/OMERO5.0__0.sql |
|
|
|
|
|
|
|
- start the upgraded server: |
|
|
|
|
|
|
|
|
