Fisheye folder layout
By default, Fisheye will create a self-contained instance directory within the <FishEye install directory> – the directory where you unzip the package. The Fisheye instance directory is where your Fisheye data is stored.
For a production environment, you should not locate your Fisheye instance directory inside the — they should be entirely separate locations. If you do put the instance directory in the <FishEye install directory> it will be overwritten, and lost, when Fisheye gets upgraded. And by the way, you'll need separate Fisheye instance directories if you want to run multiple copies of Fisheye. <FishEye install directory>
You should create your Fisheye instance directory, and then tell Fisheye where you created it by setting a FISHEYE_INST environment variable. See Installing Fisheye on Windows and Installing Fisheye on Linux and Mac for information about setting the FISHEYE_INST environment variable.
Furthermore, we recommend that the instance directory be secured against unauthorized access.
On this page:
Default Fisheye folder layout
The default Fisheye folder layout includes the Fisheye instance data inside the <FishEye install directory>. This layout is not recommended for production environments.
| Configuration file. |
| Directory under which Fisheye stores its data. |
| Persistent data. |
| Caches and indexes. |
| Log files. |
| Temporary files. |
| Caches and indexes. (and also in |
| Scripts for controling Fisheye. |
| Fisheye's dependent libraries. |
| Syntax highlighting definitions. |
| Remainder omitted for brevity. |
Recommended Fisheye folder layout
The Fisheye folder layout that we recommend for production environments has the Fisheye instance directory, which contains your instance data and is defined by FISHEYE_INST, in a completely separate location from the <FishEye install directory>.
| Configuration file. |
| All persistent and most temporary data |
| Caches and indexes (and also in |
| Site-specific Java libraries (.jars) that Fisheye should load on startup. (Do not copy the dependent |
| Site-specific syntax highlighting definitions. |
| Used for setting system properties within the Fisheye JVM, which may sometimes be useful for support purposes. (Note: the other way to set properties is using FISHEYE_OPTS, e.g.: |
| Fisheye's dependent libraries. |
| Fisheye bundled highlighting definitions. |
|
|
| Remaining files are found under |