Doc downloads (PDF, HTML & XML)
[FishEye Knowledge Base]
By default, FishEye will install and run self-contained within the <FishEye home directory>
, that is, the directory where you unzip the package. Alternatively, you can create a separate FishEye "instance" directory outside of the <FishEye home directory> and reference it with an environment variable, FISHEYE_INST
. This may be necessary for practical or administrative reasons. Here are our recommendations for some of these possible scenarios:
Number of Instances | Installation Type | Upgrade Likelihood | Separate FishEye Instance Directory |
---|---|---|---|
Single | Production | Highly Recommended | |
Single | Development | Likely | Highly Recommended |
Single | Development | Not Likely | Unnecessary |
In order to run multiple instances of FishEye on the same server, it is mandatory to establish a separate FISHEYE_INST
directory.
Number of Instances | Installation Type | Upgrade Likelihood | Separate FishEye Instance Directory |
---|---|---|---|
Multiple | Prod. / Dev. | N/A | Mandatory |
See the differences between FishEye folder layouts depending on which installation you choose.
For production installations, we recommend that the FishEye instance directory be secured against unauthorised access.
As outlined in Method 3 of our FishEye upgrade guide, you can separate your FishEye instance data (to make future upgrades easier) even if initially you chose not to do so:
FISHEYE_INST
environment variable./
FISHEYE_INST
:<FishEye home directory>/config.xml
<FishEye home directory>
/
var
<FishEye home directory>
/
cache
<FishEye home directory>
/
data
(optional – if it exists)
4. Start the FishEye/Crucible instance.