All Versions
Fisheye 4.2 DocumentationFisheye 4.1 Documentation
Fisheye 4.0 Documentation
More...
To configure the server settings, click 'Server Settings' on the 'Admin Menu'.
For information on configuring SSL for Fisheye, see FishEye SSL Configuration.
Some settings on this page require you to restart FishEye for changes to take effect.
Setting | HTTP Bind |
|---|---|
Description | The hostname the FishEye web server will bind to. This can take the form of a host name and port number, or you can leave the host name blank. If no host name is specified, then FishEye will bind to all available interfaces. |
Examples | You can use bindings like the following:
|
Restart required | Yes |
Setting | Web context |
|---|---|
Description | By default, the FishEye application can be accessed via |
Example | If you specify a web context of 'fisheye' then FishEye will be accessible from |
Restart required | Yes |
Setting | Proxy scheme |
|---|---|
Description | Can be set if you are forwarding through to FishEye from another web server. If you set proxy values, you must also add a matching site URL (see below). |
Example | Valid settings are |
Restart required | Yes |
Setting | Proxy host |
|---|---|
Description | Can be set if you are forwarding through to FishEye from another web server. If you set proxy values, you must also add a matching site URL (see below). |
Example | A valid setting would be |
Restart required | Yes |
Setting | Proxy port |
|---|---|
Description | Can be set if you are forwarding through to FishEye from another web server. If you set proxy values, you must also add a matching site URL (see below). |
Example | The port number of the web server, an integer from 0 through 32,765. |
Restart required | Yes |
Setting | AJP13 Bind |
|---|---|
Description | The bind host name for ajpv13. If no host name is specified, then FishEye will bind to all available interfaces. |
Examples | You can use bindings like the following:
|
Restart required | Yes |
Setting | Remote API |
|---|---|
Description | Enables/disables FishEye's Remote API. Clicking on the help link will take you to the API doc. |
Example | 'On' enables the Remote API. |
Restart required | No |
Setting | Server timezone |
|---|---|
Description | The time zone to use within FishEye. This time zone is used when displaying dates and parsing EyeQL date expressions. If blank, then the time zone of the server running FishEye is used. |
Example | This defaults to the FishEye server's time zone, but you can select another zone from the drop-down list. |
Restart required | No |
Setting | Site URL |
|---|---|
Description | The base URL for this FishEye instance. If not specified, FishEye will attempt to determine this value. You need to set this if you are forwarding through to FishEye from another web server, or if FishEye does not correctly determine the host name you want FishEye users to see FishEye on. Fisheye uses this URL to generate links in notification E-mails. If you have set a proxy scheme/host/port, the values used there must match the site URL. Do not include a trailing slash ('/') at the end of the URL. |
Example | http://www.example.com/apps/fisheye |
Restart required | No |
See also Subversion Client settings.
2 Comments
Jeffrey Silverman
Feb 20, 2010How can I set up JIRA+Fisheye follows:
How do I set up that last bit? I imagine that web context and proxy * settings need to be set up roughly as described above, but how do I configure JIRA to alias "/fisheye" to Fisheye?
For that matter, how would I set up Apache to use the web and proxy settings of Fisheye to point to Fisheye?
I hope that is clear.
I'm an examples person, so if anyone could post examples of the solutions to these questions, that'd be great.
Jeffrey Silverman
Nov 29, 2010Hi, Jeff. I am answering my own question.
Solution: use another web server, running on port 80, as a reverse proxy, and put JIRA, Crucible, and any other Atlassian services on their own ports. Or alias "/fisheye" or similar to a reverse-proxied end point. I set this up using Nginx but Apache works similarly, and all the Atlassian docs use Apache in their examples.