I can say our instance of reviewboard isn't on port 80 and our database
isn't named reviewboard. It works here just fine
On Aug 12, 2011 5:30 PM, "Kannaiyan Natesan" wrote:
> Christin,
>
> Bug is on the ReviewBoard.
>
>
> 1. Reviewboard cannot run on other http ports other than 80. If you want
> t
Hi,
I'm not sure how you tested that, but I can assure you that neither
condition is true of Review Board. All of our own Review Board instances
have names other than "reviewboard" and I frequently run instances for
testing that use other ports.
More likely, there's some setup problem or a bug in
Christin,
Bug is on the ReviewBoard.
1. Reviewboard cannot run on other http ports other than 80. If you want
to run on other ports Apache Mod-Proxy might help.
2. The database should be 'reviewboard' trying to install in other
database names will fail.
Tested with "hg postreview"
On Fri, 2011-08-12 at 11:38 -0700, Eric Hanchrow wrote:
> I'm looking at a review from a co-worker, and I'd really like to have
> her code on my development machine, so that I can run the unit tests
> and mess around generally.
>
>
>
> I figured that I'd be able to download the diff from the rev
I'm looking at a review from a co-worker, and I'd really like to have her
code on my development machine, so that I can run the unit tests and mess
around generally.
I figured that I'd be able to download the diff from the review
(http://our-reviewboard.server/r/123/diff/raw/) and apply that to
On Thu, 2011-08-11 at 14:39 -0700, D. Peterson wrote:
> Thanks Chris,
>
> Our IT chief identified the problem. Selinux is exactly what it was.
> We had completely opened up the iptables on installation as this is on
> an internal network, but didn't know about the CentOS default selinux
> setup. H
