Hey David,
I was tailing the logs after toggling activate/deactivate and I only saw:
Installing extension media for extensions_name 0.1 (enabled = True)
I can also just cp the files over each time I pip install but that does not
seem optimal.
Is there a recommended place I start for debugging the code when
investigating why this replication is not occurring?
-Jay
On Friday, September 26, 2014 2:55:01 PM UTC-7, David Trowbridge wrote:
>
> Deactivating/reactivating should do it. Can you look in the reviewboard
> log file and see if there's anything related in there?
>
> -David
>
> On Fri, Sep 26, 2014 at 5:52 PM, Jay Lee <jaylee...@gmail.com
> <javascript:>> wrote:
>
>> Hey David,
>>
>> I checked the directoy and noticed that only roughly half my extensions
>> were replicated over to that directory.
>>
>> Is there a way to retrigger the replication as activating/deactivating on
>> the admin panel doesn't appear to do so?
>>
>> Extensions that were not replicated seem to also work except for the
>> static files not being discovered.
>>
>> Thanks again,
>> Jay
>>
>> On Friday, September 26, 2014 2:31:15 PM UTC-7, David Trowbridge wrote:
>>>
>>> Jay,
>>>
>>> Yes, that's correct. If you look in the "ext" directory in the
>>> htdocs/media/ext directory after enabling your extension, you should see
>>> your media file. Your apache config should have an alias for /media to
>>> point to the htdocs/media directory.
>>>
>>> -David
>>>
>>> On Fri, Sep 26, 2014 at 5:24 PM, Jay Lee <jaylee...@gmail.com> wrote:
>>>
>>>> Hi David,
>>>>
>>>> I have used media bundles I believe.
>>>>
>>>> My extension looks like:
>>>>
>>>> class Defaults(Extension):
>>>> metadata = {
>>>> 'Name': 'defaults',
>>>> 'Summary': 'fdsa',
>>>> }
>>>>
>>>> js_bundles = {
>>>> 'default': {
>>>> 'source_filenames': ['js/customize.js']
>>>> }
>>>> }
>>>>
>>>> and was generated with the boilerplate generator.
>>>>
>>>> Is that not a correct usage?
>>>>
>>>> I activated the extension via the admin interface and used 'pip
>>>> install' to get it recognized with RB.
>>>>
>>>> thanks,
>>>> Jay
>>>>
>>>> On Friday, September 26, 2014 2:14:06 PM UTC-7, David Trowbridge wrote:
>>>>>
>>>>> Jay,
>>>>>
>>>>> If you have your extension media defined using the media bundles[1],
>>>>> when you activate an extension, Review Board will copy the static media
>>>>> into your htdocs/static directory.
>>>>>
>>>>> [1] https://www.reviewboard.org/docs/manual/2.0/extending/ex
>>>>> tensions/static-files/
>>>>>
>>>>> -David
>>>>>
>>>>> On Fri, Sep 26, 2014 at 5:01 PM, Jay Lee <jaylee...@gmail.com> wrote:
>>>>>
>>>>>> Hello!
>>>>>>
>>>>>> I have upgraded to reviewboard 2.0.7 and have been actively working
>>>>>> on extensions. However, I have not been able to find a "good" way of
>>>>>> exposing my extension's static files.
>>>>>>
>>>>>> The issue I am running into is that my reviewboard installation
>>>>>> relies on a 'apache-wsgi.conf' that has the following:
>>>>>>
>>>>>> Alias /static "/export/apps/reviewboard/site/htdocs/static"
>>>>>> <Location "/static">
>>>>>> SetHandler None
>>>>>> </Location>
>>>>>>
>>>>>> This means that when an extension is pip installed it ends up in
>>>>>>
>>>>>> /export/apps/reviewboard//lib/python2.6/site-packages/extens
>>>>>> ion_name/static/js/default.min.js
>>>>>>
>>>>>> which does not have the prefix
>>>>>>
>>>>>> /export/apps/reviewboard/site/htdocs/static
>>>>>>
>>>>>> This causes all my static files to be rejected by the apache web
>>>>>> server.
>>>>>>
>>>>>> Is there an recommended or clean way of addressing this issue?
>>>>>>
>>>>>> Thanks,
>>>>>> Jay
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Get the Review Board Power Pack at http://www.reviewboard.org/pow
>>>>>> erpack/
>>>>>> ---
>>>>>> 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 email to reviewboard...@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> --
>>>> 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 email to reviewboard...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> 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
>> email to reviewboard...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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 email
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
