The main idea behind two versions (as far as I have been told) is that they
want to keep old version of ReviewBoard while users get used to the new one
and to be able to go back if needed...
Why it is not recommended to use virtualenvs in production environment?
(as said here: http://www.reviewboard.org/docs/codebase/dev/getting-started/
ceturtdiena, 2013. gada 26. septembris 19:24:45 UTC+2, Christian Hammond
> Sorry for the late response. Never saw this reply.
> There are no tutorials I'm aware of for setting up a virtualenv, and it's
> not something we currently support.
> You are not going to be able to have differing versions of Review Board on
> one server easily. I expect you will repeatedly have trouble. I *strongly*
> recommend you get a second server, or look into a VM solution (like VMware
> Workstation's server mode), in order to properly separate them.
> I'm not sure why you need two servers, though. Can you explain the need
> for that? Generally, you could just use the Local Sites feature or private
> repos/groups to separate access between people.
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
> > wrote:
>> Thank You for replying :)
>> Maybe there is some tutorial/instruction/example how to use virtualenvs
>> to achieve something like this?
>> Well for now one version is RB 1.7.13 and other the same RB 1.7.13 (but
>> with some modifications), but as far as I have been told first will be
>> changed to earlier 1.7 (or even 1.6) release. For now my goal is to check
>> how easy it is to run two different ReviewBoard version from one server and
>> it is not important which two versions I use...
>> Here I found something similar to my problem:
>> I tried to set up Apache virtualhost but so far without luck (doing some
>> additional reading on that right now). Is it even possible to achieve my
>> goal this way?
>> Separately (I mean using only one RB version on server) it kind of works,
>> but when I try to use both only one (first in the virtualhost list) web
>> page is accessible..
>> But there is one other issue with situation when one version is used on
>> server - when I install original ReviewBoard version I'm no more able to
>> access the modified version (although virtualhost .conf links to the
>> modified version). And when I re install modified version original is
>> inaccessible. Maybe You know if there is some file overwritten during
>> installation that is responsible for this?
>> Once more, thank You!!
>> piektdiena, 2013. gada 13. septembris 06:30:32 UTC+2, Christian Hammond
>>> One option is to use virtualenvs, which will let you fully separate out
>>> your set of Python packages. This isn't something we document or really
>>> support right now, though, and it's a bit advanced.
>>> Another is to install on a separate server/VM, which will fully let you
>>> separate entire configs.
>>> What two versions are you trying to use?
>>> On Thursday, September 12, 2013, robcikss wrote:
>>>> My current project involves migrating some of our implemented feature
>>>> (that our office uses) from older reviewborad release to newer. But it is
>>>> required that for now both reviewboard versions should be running, while
>>>> migration is going on. As I'm new to reviewboard development and it's
>>>> I have no idea how I could achieve this. I tried to google it but without
>>>> Actually I tried to install two different reviewboard version, but it
>>>> seems that only one of them is accessible (the later one installed). I
>>>> taught that changing the .conf file in /etc/apache2/sites-enabled should
>>>> enough but after changing it and restarting apache server and memcached,
>>>> the same reviewboard version is still running not the other.
>>>> I am using apache server (on localhost), memcahed, mod_wsg on Ubuntu
>>>> I would appreciate any help
>>>> Thank You,
>>>> Get the Review Board Power Pack at http://www.reviewboard.org/**
>>>> powerpack/ <http://www.reviewboard.org/powerpack/>
>>>> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
>>>> Happy user? Let us know at
>>>> You received this message because you are subscribed to the Google
>>>> Groups "reviewboard" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to reviewboard+unsubscribe@**googlegroups.com.
>>>> For more options, visit
>>> Christian Hammond - chi...@chipx86.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
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> For more options, visit https://groups.google.com/groups/opt_out.
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/groups/opt_out.