• fassembler discussion

  • Re: [operations discussion] new wordpress-req.txt file

    from darcy on May 22, 2008 12:04 PM 
    Cool -- while we're on the subject, any chance I can use this to peg a
deployment to a particular version of our wordpress code?  We always
install from trunk and that's a bit unsatisfactory.

egj

On Thu, May 22, 2008 at 11:57 AM, Robert Marianski
<rmarianski@...> wrote:
> I added a new topp_wordpress_theme variable to the build that controls
> which wordpress theme to use for the project blogs. It should be set to
> "openplans" for openplans themes, and "livablestreets" for woonerf
> themes.
>
> topp_wordpress_theme will show up in etc/build.ini and it's set in the
> wordpress-req.txt file. It defaults to openplans if not set.
>
> --
> Robert
>
>
>
> --
> Archive: http://www.openplans.org/projects/operations/lists/operations-discussion/archive/2008/05/1211471867008
> To unsubscribe send an email with subject unsubscribe to operations-discussion@....  Please contact operations-discussion-manager@... for questions.
>
>
    Thread Outline:

  • Re: Re: [operations discussion] new wordpress-req.txt file

    from rmarianski on May 22, 2008 12:22 PM 
    On Thu, May 22, 2008 at 12:04:41PM -0400, Ethan Jucovy wrote:
> Cool -- while we're on the subject, any chance I can use this to peg a
> deployment to a particular version of our wordpress code?  We always
> install from trunk and that's a bit unsatisfactory.
> 
> egj

That's a good idea. We should specify the repository like we specify
them for other requirements. It can be trunk at a particular revision
using the poach eggs syntax.

-- 
Robert

    • Re: Re: [operations discussion] new wordpress-req.txt file

      from ianb on May 22, 2008 12:27 PM 
      Robert Marianski wrote:
> On Thu, May 22, 2008 at 12:04:41PM -0400, Ethan Jucovy wrote:
>> Cool -- while we're on the subject, any chance I can use this to peg a
>> deployment to a particular version of our wordpress code?  We always
>> install from trunk and that's a bit unsatisfactory.
>>
>> egj
> 
> That's a good idea. We should specify the repository like we specify
> them for other requirements. It can be trunk at a particular revision
> using the poach eggs syntax.

I think it'll try to install the result, and of course there's nothing 
to install.  In other cases the repository has just been a setting.  I 
believe you could pretty much make this work by changing the default 
wordpress_repo value to '{{project.req_settings.get("wordpress_repo", 
"default_repo")}}'.

We could change the installation process to just not install checkouts 
if there's no setup.py.  My only worry is that in most cases a missing 
setup.py would be an error of some sort (though I can't recall 
encountering this error, so maybe it's not a likely mistake).

   Ian

      • Re: Re: [operations discussion] new wordpress-req.txt file

        from magicbronson on May 22, 2008 04:31 PM 
        On Thu, May 22, 2008 at 12:27 PM, Ian Bicking <ianb@...> wrote:

> Robert Marianski wrote:
>
>> On Thu, May 22, 2008 at 12:04:41PM -0400, Ethan Jucovy wrote:
>>
>>> Cool -- while we're on the subject, any chance I can use this to peg a
>>> deployment to a particular version of our wordpress code?  We always
>>> install from trunk and that's a bit unsatisfactory.
>>>
>>> egj
>>>
>>
>> That's a good idea. We should specify the repository like we specify
>> them for other requirements. It can be trunk at a particular revision
>> using the poach eggs syntax.
>>
>
> I think it'll try to install the result, and of course there's nothing to
> install.  In other cases the repository has just been a setting.  I believe
> you could pretty much make this work by changing the default wordpress_repo
> value to '{{project.req_settings.get("wordpress_repo", "default_repo")}}'.


this was done in r17218. note the NOTE in the commit message:

try to retrieve the wordpress download location from new setting
> 'wordpress_repo' before defaulting to trunk. NOTE: the url can be given as
> https://path/to/wordpress/trunk@XYZ to specify revision XYZ
>

and wordpress_repo was added to the trunk wordpress-req.txt files in r17219.

We could change the installation process to just not install checkouts if
> there's no setup.py.  My only worry is that in most cases a missing setup.py
> would be an error of some sort (though I can't recall encountering this
> error, so maybe it's not a likely mistake).
>
>  Ian
>
>
> --
> Archive: http://www.openplans.org/projects/fassembler/lists
> /fassembler-discussion/archive/2008/05/1211473678142
>
> To unsubscribe send an email with subject unsubscribe to
> fassembler-discussion@....  Please contact
> fassembler-discussion-manager@... for questions.
>
>
Return to conversation view