Issue 1182 in reviewboard: Apache configuration file is misconfigured, if RB do not goes to root.
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1182 by msu...@redhat.com: Apache configuration file is misconfigured, if RB do not goes to root. http://code.google.com/p/reviewboard/issues/detail?id=1182 What version are you running? 1.5 What's the URL of the page containing the problem? installation What steps will reproduce the problem? 1. install ReviewBoard (RB) on Linux 2. create new sit in /www/spacewalk-reviewboard and url will be /spacewalk/reviews 3. check /www/spacewalk-reviewboard/conf/apache-modpython.conf What is the expected output? What do you see instead? Location and Alias directives use /, whereas there obviously should be /spacewalk/reviews What operating system are you using? What browser? Debian -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1182 in reviewboard: Apache configuration file is misconfigured, if RB do not goes to root.
Updates: Status: NotABug Comment #1 on issue 1182 by chipx86: Apache configuration file is misconfigured, if RB do not goes to root. http://code.google.com/p/reviewboard/issues/detail?id=1182 This is actually by design in order to support some existing setups and older versions of Django. We may move away from this at some point, but for now, it's intentional. The default configuration of Review Board expects to own the subdomain, and then the site root is calculated at runtime. You're always free to modify the generated configuration files. The reason for this is that before, Django was unable to work in subdomains without some hacks. We put some stuff in place to allow working in subdomains, and changing our way of doing it now would break existing installs that rely on our workarounds. Moving away from that is going to be a larger effort. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
