Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,365
Community Members
 
Community Events
168
Community Groups

Fisheye/Crucible config.xml Webcontext to /fisheye

In my FISHEYE_INST/config.xml, I'm trying to set the right values in the web-server section. I'd like my users to be able to do http://hostname/fisheye (and me to do .../fisheye/admin). This is a default/new install of Crucible/Fisheye 2.8.1 with Apache 2.2.15 on RHEL6/64bit running on port 80 using the docs at https://confluence.atlassian.com/display/FISHEYE/Integrating+with+other+web+servers and https://confluence.atlassian.com/display/FISHEYE/Configuring+the+FishEye+web+server

I beileve it should be

<web-server site-url="http:/hostname/" context="fisheye">
<http bind=":8060" proxy-host="hostname" proxy-port="80"/>
</web-server>

Behaviorally, the above appears to work. However, the first docs refer to "web context" (in bold, no less). The second set of docs imply web context should be in with the http section and not the web-server section. Furthermore, the second set of docs specifically state it should not have the trailing slash, and that the "fisheye" part of my URL should go there rather than in the webcontext section. In particular, when I first installed Crucible, I had it all running at the top level (http://hostname) and when I set the Site-URL there, I set it to http:/hostname/fisheye and saved it. It modified my config.xml to be site-url="http://hostname/fisheye" but never placed any webcontext in place.

In any case, I just wanted a touch of clarity on how that should work.

Thank you,
PH

2 answers

1 accepted

2 votes
Answer accepted

Yep. In my particular case, I finally settled on "<web-server site-url="http://hostname/fisheye" context="fisheye"> ...otherstuff... </webserver>

I'm now at Fisheye/Crucible 2.9.1, still on RedHat6/64bit and Apache 2.2.15. I suspect the F/C version probably doesn't matter too much, but just wanted to note that I'm no using the version originally mentioned in my first post.

PH

Did this end up working for you? I'm having the same issue.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events