Hi,
I've been running a reviewboard instance in our network for testing
purpose. It was being accessed as: http://hostname.example.com/reviews
Now I would like to move this installation to production and would
like to change the URL to http://reviews.example.com/ - how can I
achieve this?
I trie
Hi,
As I've mentioned in my earlier email, I'm moving one of our
ReviewBoard instances to production. One of the teams has been using
another (local) RB instance till now and would like to merge their
requests to this new production instance.
If my understanding is correct, I've 2 options to merg
e
> this, but we have our hands full and it's unlikely we will in the near
> future.
>
I'm still very new to DJango and RB. I'll see what I can do here.
Unfortunately, can't confirm / commit anything as of now. :(
Srinidhi.
>
> On Fri, Mar 26, 2010 at 12:54 AM,
, but did you change the hostname in
> the Admin UI -> General Settings page?
>
Doh! Didn't look there!! I was digging around more at the site config :(
Will remember this for the next time :)
Thanks,
Srinidhi.
>
>
> On Thu, Mar 25, 2010 at 3:30 PM, Srinidhi B S
Hello Christian,
On Wed, Jul 27, 2016 at 4:34 PM, Christian Hammond
wrote:
> Hi Abhi,
>
> Please give the attached build of django-evolution a try, and see if it
> allows you to upgrade. You'll want to start fresh from the backup of your
> database.
>
This attached build of django_evolution work
Hello Everyone,
I'm (finally!) preparing to upgrade our very old ReviewBoard instance
from 1.0.6 to 2.0.12. I've been worried / concerned about the upgrade
path.
Around this time last year, I did attempt an upgrade from 1.0.6
directly to 1.7.6 and things seemed to have worked out fine. But I
coul
1.0.x over to
2.0.x?
Any hints as to how I can go about resolving these errors? Even hints
/ tips on how to debug the issue would be very helpful.
Regards,
Srinidhi.
On Thu, Jan 29, 2015 at 10:39 PM, Srinidhi B S wrote:
> Hello Everyone,
>
> I'm (finally!) preparing to upgrade our v
Hi,
On Thu, Jan 29, 2015 at 10:39 PM, Srinidhi B S wrote:
> Hello Everyone,
>
> I'm (finally!) preparing to upgrade our very old ReviewBoard instance
> from 1.0.6 to 2.0.12. I've been worried / concerned about the upgrade
> path.
>
> The following are the cha
it's likely to break things pretty badly (in particular, file-attachment
>> only review requests). Christian, any thoughts on what's causing the errors?
>>
>> -David
>>
>> On Fri, Feb 27, 2015 at 7:40 AM Srinidhi B S
>> wrote:
>>>
>>
Wow! Thanks a lot for the quick response, Christian! Really appreciate it!
On Sun, Mar 8, 2015 at 2:58 PM, Christian Hammond
wrote:
> Okay, I guess I was a bit confused here by which versions you're trying when.
>
> The "Django Evolution is too new" issue would apply if upgrading to a 1.7.x
> re
Hey Christian,
On Sun, Mar 8, 2015 at 3:45 PM, Christian Hammond
wrote:
> This is one advantage for companies with support contracts -- all information
> is in one place, so we can easily look it all up, merge related discussions,
> store additional information on your setup, etc. Plus, we ha
Hey Christian,
On Sat, Apr 4, 2015 at 11:05 AM, Christian Hammond
wrote:
> Hey Zach,
>
> I basically have this fixed, and will be getting it through a review cycle
> and ready for a new django_evolution release, but I have some concerns about
Thank you so much for identifying the issue and prepa
12 matches
Mail list logo
