Robert,

It's easiest (and safest) to develop extensions using a development
environment for Review Board rather than a production deploy. We have
instructions for creating a dev environment at
https://www.reviewboard.org/docs/codebase/dev/getting-started/

-David

On Wed, Oct 21, 2015 at 2:09 PM, Robert Bolen <bolen2...@gmail.com> wrote:

> David,
>
> When doing the upgrade from 1.7.6 to 2.0.20 using the easy_install command
> I received no errors as I previously stated. In order to create the
> extensions you recommended which utilizes the contrib directory, this was
> not installed when upgrading review board. Does this directory need to be
> installed separately from the review board .egg file?
>
> -Robert
>
>
> On Wednesday, October 21, 2015 at 9:20:03 AM UTC-6, Robert Bolen wrote:
>>
>> David,
>>
>> When doing the extension what would the right file path for this
>> extension and does another file call it or does it need a specific name?
>>
>> -Robert
>>
>> On Tuesday, October 20, 2015 at 2:14:07 PM UTC-6, David Trowbridge wrote:
>>>
>>> Robert,
>>>
>>> You can either do it as part of an extension, or just using entry
>>> points. See
>>> https://www.reviewboard.org/docs/manual/2.0/extending/auth-backends/#packaging
>>>
>>> -David
>>>
>>> On Tue, Oct 20, 2015 at 9:15 AM, Robert Bolen <bole...@gmail.com> wrote:
>>>
>>>> David,
>>>>
>>>> How would I go about doing that? I'm new to python why I went the route
>>>> that I did.
>>>>
>>>> -Robert
>>>>
>>>> On Monday, October 19, 2015 at 2:29:03 PM UTC-6, David Trowbridge wrote:
>>>>>
>>>>>
>>>>> On Mon, Oct 19, 2015 at 1:25 PM, Robert Bolen <bole...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> 'Mantis User Database'
>>>>>
>>>>>
>>>>> This is not part of the upstream Review Board code. It looks like you
>>>>> have some custom modifications that are broken.
>>>>>
>>>>> There's no reason to ship additional authentication backends as a
>>>>> patch to Review Board. You can write them in a separate python package and
>>>>> use entry points to register them. This way you can maintain it outside of
>>>>> the Review Board codebase without worrying about patching problems like
>>>>> this.
>>>>>
>>>>> -David
>>>>>
>>>> --
>>>> Supercharge your Review Board with Power Pack:
>>>> https://www.reviewboard.org/powerpack/
>>>> Want us to host Review Board for you? Check out RBCommons:
>>>> https://rbcommons.com/
>>>> Happy user? Let us know! https://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 email to reviewboard...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://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
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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 email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to