Everything externally facing is currently running on isda-maven1. There are two server stacks running, the Fisheye server (which is their own hacked-up Tomcat running out of /home/fisheye) and a conventional apache+tomcat setup that serves up Artifactory and OpenGrok.
If it breaks:
Try restarting; "/etc/init.d/web stop" will take down all of the above services, and "... start" will bring them all back. Some of them take quite a while to shut down, so make sure there are no running java processes before you restart.
If OpenGrok stops updating:
Every other hour, cron runs /home/opengrok/update-indices.sh, which logs to .../update-indices.log. All it's doing is a subversion checkout followed by a run of the update script; it should be fairly bombproof.
If Fisheye stops updating:
If it's not running at all, restart it per the above. Otherwise, everything is done via the GUI; the administration site is here, and you'll need the admin password, which is noted in /home/fisheye/README.access.
Adding browsable repositories:
For Fisheye, this is easy, it's all by-the-book using the GUI. Mostly you just need the repository URL. Note that we only want to run it against public repositories for now.
Each repository indexed by opengrok is served by a separate web application running on isda-maven1.mit.edu. To deploy a new application, you need to:
- check out the source tree under /home/opengrok/src/<name>
- make a copy of the indexing script that references the new names
- index that source tree into /home/opengrok/data/<name>
- add checkout/index maintenance to the cron job
- add apache httpd.conf mod_jk glue for the new application
- configure an instance of the web application to refer to the source and data directories defined above
- install it in the source subdirectory of tomcat's webapp directory
- add apache httpd.conf mod_jk glue for the new application
- restart tomcat and httpd