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 listening on port 8060, its default) and a conventional apache+tomcat setup that serves up Artifactory and OpenGrok. It's all linked to from the static html page served by apache from its htdoc directory.
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.
...
- 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
Modifying opengrok applications:
The location for .war development for OpenGrok applications is in /home/opengrok/wars. You may want to modify the application to change, for instance, the appearance of header banners, icons, links, or whatever. Let's say you wanted to change the krb5 opengrok setup: you'd run:
- cd /home/opengrok/wars/krb5
Wiki Markup \[edit stuff\]- zip -r ../krb5.war *
- cp -f ../krb5.war /home/apache-tomcat-5.5.25/webapps/
Tomcat will automatically notice the new .war within a few seconds and unpack it; no further action is needed.