We are trying to do an evaluation of ReviewBoard.
I have setup ReviewBoard via the Docker container, wih SSL termination
through a reverse proxy. the website seems to work fine, and direct
queries to the API via curl work fine. I am able to use 'rbt setup-repo'
to configure a repo.
However,
a similar report recently and plan
> to look into it for the next patch release.
>
> What happens if you don't pass --username and --password? It should
> prompt you for login at that point, and properly store the session
> information.
>
> Christian
>
> On Thu, Nov
Our reverse proxy is configured to redirect https://ourdomain.com/review to
ReviewBoard. I have configured nginx to properly host /review/static and
/review/media and configured site_root to use /review and In the admin
panel set the URL to https://ourdomain.com/review
This seems to work as I
Thanks, I rebuilt from the release-6.x branch and the issue is resolved
On Friday, November 3, 2023 at 8:59:03 AM UTC-7 David Trowbridge wrote:
> This is a known issue in 6.0, and we'll be putting out a 6.0.1 very soon
> that fixes it.
>
> David
>
> On Fri, Nov 3, 20
My 1st attempt at setting up ReviewBoard via docker, I tried to host on a
non-standard port http://ourdomain.com:8900
I configured nginx apropriately, and set the port in the Admin UI. This
allowed the website to work propelry. However, when accessing
http://ourdomain.com:8900/api all of the
umber?
>
> David
>
> On Fri, Nov 3, 2023 at 12:21 PM geof...@gmail.com
> wrote:
>
>> My 1st attempt at setting up ReviewBoard via docker, I tried to host on a
>> non-standard port http://ourdomain.com:8900
>>
>> I configured nginx apropriately, and set the p
He have a post-push workflow where we want to trigger a review on already
pushed data in a git repo. The upstream branch is not linear, and so 'rbt
post' often fails due to this. We can instead use 'rbt post -S' to squash
the commits and this is fine for our needs, but our workflow actually
