Tails

#1 Updated by drebs 2017-03-08 20:05:49

This branch adds a commit to create the staging repository and make sure it merges all updates made to main weblate repository: https://0xacab.org/drebs/puppet-tails/commits/12311/create-staging-and-update-hook

#2 Updated by intrigeri 2017-03-08 20:11:22

Hi!

> This branch adds a commit to create the staging repository and make sure it merges all updates made to main weblate repository: https://0xacab.org/drebs/puppet-tails/commits/12311/create-staging-and-update-hook

If that’s a pull request: thanks! Please ask emmapeel to teach you how to request a review (or I can point you to the relevant doc).

Otherwise: sorry for the noise. I’ll shut up until I’m asked to do something :)

#3 Updated by drebs 2017-03-09 10:28:12

intrigeri wrote:
> Hi!
>
> > This branch adds a commit to create the staging repository and make sure it merges all updates made to main weblate repository: https://0xacab.org/drebs/puppet-tails/commits/12311/create-staging-and-update-hook
>
> If that’s a pull request: thanks! Please ask emmapeel to teach you how to request a review (or I can point you to the relevant doc).
>
> Otherwise: sorry for the noise. I’ll shut up until I’m asked to do something :)

Hey, thanks for noticing.

We plan to add more to that branch to make it cover the whole automated ikiwiki build process for the staging translation website. We thought about start tackling the problem in one direction for now (weblate -> staging git -> staging ikiwiki) and only that is working we start thinking about the other direction (ikiwiki builds modify staging git and maybe we want that to modify weblate and the main tails website git repo).

So it is still not a pull request. But we already have some doubts, and if you can help with those it is already great for now!

The recipe we started to write that builds the staging git repository depends on the existence of the main weblate git repository. But the main weblate git repo was manually created during weblate configuration through web interface and is currently not covered by puppet. If that is not included in puppet, a run of the recipe in a fresh server would fail until the project is manually created and a repo is available in the expected path.

Should we also think on a way to automatically create the weblate project (through puppet) that creates/clones the main weblate git repository by using django/weblate scripts? That would be necessary in case of a fresh installation without human intervention.

More questions will come. ;) Thanks!

#5 Updated by Anonymous 2017-03-13 17:32:05

drebs wrote:

> The recipe we started to write that builds the staging git repository depends on the existence of the main weblate git repository. But the main weblate git repo was manually created during weblate configuration through web interface and is currently not covered by puppet. If that is not included in puppet, a run of the recipe in a fresh server would fail until the project is manually created and a repo is available in the expected path.

> Should we also think on a way to automatically create the weblate project (through puppet) that creates/clones the main weblate git repository by using django/weblate scripts? That would be necessary in case of a fresh installation without human intervention.

I think our main idea was indeed that we could easily recreate and re-setup a weblate instance (what you call main weblate repository). This could also help other projects reuse our work and also help us recreate a VM easily.

So basically, such a script would be more than welcome.

However, it feels to me like this might be a little bit overengineered and I’m not sure how realistic such a thing would be at all.

#6 Updated by Anonymous 2017-03-14 08:49:02

/code/attachments/download/1551/weblate.svg should reflect the latest design.