On July 9, 2014 at 1:50:31 PM, Michael Kopp (michael.f.k...@googlemail.com)
> On July 7, 2014 at 11:06:38 AM, Michael Kopp (michael.f.k...@googlemail.com)
>> I've been trying to set up review-board on a lighttpd-server (v1.4.35)
>> under arch linux. I managed to set it up to display something, but
>> unfortunately all the static data such as css, images and js are not
>> loaded. In the logs I see that they are not found. Attached you can
>> find many config files and some logs; `ls' holds the directory
>> listings. If I try to enter a file, that got a 404-reply, directly as
>> url, for example
>> (my server is called virtualarch, the installation is under
>> /srv/http/rbex3, made by rb-site install) I get (with DEBUG=True [the
>> situation does not change if I use DEBUG=False, apart from the nice
>> 404-page.]) the following
>> Page not found (404)
On Mon, Jul 07, 2014 at 11:51:05AM -0700, Christian Hammond wrote:
> How did you install Review Board?
I installed it as an Arch-Linux AUR package -- basically,
python2 setup.py install --root=/usr
was called with the sources from ReviewBoard-2.0.2.tar.gz.
I assume you therefore had proper versions of uglifyjs and lesscss
> This is what I’d expect to see if you have a production install
> without having your web server handling static/ properly.
I'm sorry, but I don't quite get you. How can I check, whether my web
server handels static/ properly? Turning off the review-board .fcgi and
checking, whether all static conetnt is reachable?
You need a rule in your webserver config that handles /static/ and points it to
the correct place on your file system, since Review Board doesn’t handle that
path. This is completely outside the realm of Review Board.
> Basically, Review Board is not expected to handle static/ (nor should
> it) unless it’s a development install straight out of the source tree.
I don't get that either, sorry: You mean, if I had not installed the
package, but just used the built executable?
The /static/ path is completely disabled unless you’re running a development
(DEBUG=True) install straight out of the Git source tree (basically, an install
that is not at all suitable for production usage). This is just to help
development. Review Board should never be responsible for serving static media
files, since it’s jut too slow at it, and it’ll bog down the server.
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
Happy user? Let us know at http://www.reviewboard.org/users/
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.