Please tag themes with use-with-alaveteli-0.23

[Andrei Cristian Petcu]

Hi all,

I just noticed why the alavetelitheme and whatdotheyknow-theme did not
work on my machine (at least one of the reasons). They need to have a
tag that matches the exact version of Alaveteli.

I run Alaveteli v0.23.2.2 so Capistrano will search for
use-with-alaveteli-0.23.2.2, use-with-alaveteli-0.23.2,
use-with-alaveteli-0.23 or a branch named production. I forked both
themes but I think they need to have a tag named use-with-alaveteli-0.23
since I don't think there will be a need for a lot of changes for each
minor or quick fix version.

What do you think? How did you manage to make it work on your machines?
Or you don't deploy with Capistrano?

Thank you,
Andrei

[Henare Degan]

Like most of our projects we deploy Right To Know with Capistrano.

As part of the deployment Capistrano runs the `themes:install` rake task. That tries to checkout your theme repository at the branch specified in THEME_BRANCH, which we have set to `production`.

Our theme repository also serves as our project-specific issue tracker.

So you can change the THEME_BRANCH setting if you want to select what revision your theme is checked out at.

Cheers,

Henare

--
Henare Degan
hen...@oaf.org.au
Volunteer & worker - OpenAustralia Foundation - @OpenAustralia

--
You received this message because you are subscribed to the Google Groups "Alaveteli Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alaveteli-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[and...@ceata.org]

I also use production branch but I have to use my own fork. The thing is that the current setup pulls from my own repositories and I want to pull from mysociety. Unfortunately mysociety's repository do not have production branches. Also I prefer tags since they don't change. I want a deploy done today and one done 6 months from now to deploy the same thing.

I really li,e to avoid using my own forks :D

Andrei

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[Gareth Rees]

Hey Andrei,

I haven't tried this, but you should be able to use a commit SHA in the "branch" key, if you

want to deploy things at super-specific points. The behaviour of looking for the

`use-with-alaveteli-VERSION` tags is only a fallback if THEME_BRANCH is set as false.

With Capistrano, you can configure the repository and branch in

https://github.com/mysociety/alaveteli/blob/develop/config/deploy.yml.example#L3-L4

For the themes, you can configure the repository and branch in

https://github.com/mysociety/alaveteli/blob/develop/config/general.yml-example#L234-L265

I'm not that clear on what you currently have forked, and what you'd like to pull directly from

our repositories. Do you want to pull our default alavetelitheme directly from the mysociety

GitHub repo? Let me know if you're still having issues.

Hope that helps,

Gareth

[and...@ceata.org]

Hi Gareth,

I'll try the commit sha solution. It seems simple and elegant.

I forked alavetelitheme just to tag it and it seemed a little bit overkill. I want to have a simple and generic way to provision and deploy Alaveteli instances. I want others to use it also and that's why I want to pull from mysociaty's github repos and not andreicristianpetcu.

Thank you,
Andrei