.reviewboardrc global placement

2010-07-14 Thread Hayes, Kyle
Does the .reviewboardrc have to be in the checkout path or can we put this in a 
centralized area? I ask because we have a dev environment that we are setting 
up and each user has an account on the system. I would rather just setup this 
configuration once if possible, rather than for every user.

Kyle Hayes
Sr. Web Developer | Disney Family
Disney Interactive Media Group
818-623-3847
AIM/YIM/gTalk: mrkylehayes

It's kind of fun to do the impossible. -Walt Disney

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Re: .reviewboardrc global placement

2010-07-14 Thread Christian Hammond
Kyle and I talked about this one-on-one, but for anyone else interested,
I'll relay basically what I said.

As of now, we don't have any built-in way to do site configuration. It's
something I would like, but we'd have to figure out how to do it. Where does
post-review look for the site configuration file? Presumably you'd want it
on a network store, but post-review would have to have *some* config telling
it where to look.

So there are basically two main ways to tackle this today that I'm aware of:

1) Use a global wrapper for post-review. Instead of having users install
RBTools/post-review, provide a post-review in a standard, network-wide bin
path (assuming your network has one and that users have it in their PATH)
and use that to wrap post-review with whatever configuration options are
needed. This is used in some large deployments and works fairly well.

2) Supply/generate a .reviewboardrc file on installations that includes a
central .reviewboardrc. The .reviewboardrc file is basically just a Python
script, so it can import something else that's in the path.

The first option is probably the easiest and more hassle-free.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com


On Wed, Jul 14, 2010 at 3:00 PM, Hayes, Kyle kyle.ha...@disney.com wrote:

 Does the *.reviewboardrc* have to be in the checkout path or can we put
 this in a centralized area? I ask because we have a dev environment that we
 are setting up and each user has an account on the system. I would rather
 just setup this configuration once if possible, rather than for every user.
  *
 Kyle Hayes*
 Sr. Web Developer | Disney Family
 Disney Interactive Media Group
 818-623-3847
 AIM/YIM/gTalk: mrkylehayes

 *It's kind of fun to do the impossible.* -Walt Disney

  --
 Want to help the Review Board project? Donate today at
 http://www.reviewboard.org/donate/
 Happy user? Let us know at http://www.reviewboard.org/users/
 -~--~~~~--~~--~--~---
 To unsubscribe from this group, send email to
 reviewboard+unsubscr...@googlegroups.comreviewboard%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/reviewboard?hl=en

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en