Doc: Review updated web_install page

[bpindelski]

Please review the proposed changes.

[wmoore]

I don't think we support caching just now (disabled), so we probably want to remove:

The web framework supports caching for images, JSON data and thumbnails. This experimental implementation supports only Unix/Linux machines; additional problems may occur. 
To activate caching, you need to specify a cache location (the necessary directories will be created automatically)

and other associated text.

[wmoore]

Sync media section can be removed. Instead, edit E.g nginx conf:

        # weblitz django apps serve static content from here
       location /static {
           alias /opt/OMERO/OMERO.server-4.4.0/lib/python/omeroweb/static;
       }

[wmoore]

If I do this (NB: last / is essential)

$ omero config set omero.web.static_url /funcky_folder/

Then all the static media urls generated use this folder, E.g.

jrs-macbookpro-25107:OMERO will$ omero web start

Copying '/Users/will/Desktop/OMERO/dist/lib/python/omeroweb/webstart/static/webstart/img/icon-omero-web.png'
...

735 static files copied to '/Users/will/Desktop/OMERO/dist/lib/python/omeroweb/static'.

Starting OMERO.web... Validating models...

0 errors found
Django version 1.3.1, using settings 'omeroweb.settings'
Development server is running at http://0.0.0.0:4080/
Quit the server with CONTROL-C.
[09/Jul/2012 13:24:14] "GET /webclient/login/?url=%2Fwebclient%2F HTTP/1.1" 200 3543
[09/Jul/2012 13:24:15] "GET /funcky_folder/webgateway/css/reset.css HTTP/1.1" 304 0
[09/Jul/2012 13:24:15] "GET /funcky_folder/webgateway/css/ome.body.css HTTP/1.1" 304 0

Seems like the ONLY thing this command does is change the url that the browser sees, but not how / where the files are served.

The bin/omero web start command caused all the static files to be copied to dist/lib/python/omeroweb/static (running development server) but if I rm -rf dist/lib/python/omeroweb/static* while the development server is running, this has no affect on static files, so I assume they're not being used from there. So, why are they being copied there?

[wmoore]

Ah- I see #7273 covers caching & static file docs. I've removed the old caching settings (we never did support caching, right? Do we support it now?

Chris, maybe I can had over to you, since I am guessing the static_url setting (above) only has some meaning when you're deploying for real (nginx / apache conf)?

I've removed

[cxallan]

Completed.