Task #11723 (new)
Opened 11 years ago
Last modified 10 years ago
FORCE_SCRIPT_NAME required to deploy web — at Version 1
| Reported by: | atarkowska | Owned by: | atarkowska |
|---|---|---|---|
| Priority: | critical | Milestone: | 5.0.0-rc1 |
| Component: | Deployment | Version: | 4.4.9 |
| Keywords: | n.a. | Cc: | web-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by atarkowska)
While deploying multiple instances of OMERO.web in the same hardware I noticed that standard configuration is not enough. It requires few adjustments:
- setting FORCE_SCRIPT_NAME
- ngingx config:
fastcgi_split_path_info ^(/omero)(.*)$;
fastcgi_pass 0.0.0.0:14080;
fastcgi_param PATH_INFO $fastcgi_path_info;
fastcgi_param SCRIPT_INFO $fastcgi_script_name;
# fastcgi_param PATH_INFO $fastcgi_script_name;
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
