Project

General

Profile

Feature #11760

Feature #15085: Document our translation platform infrastructure

Document the entire weblate installation & setup process

Added by Anonymous over 3 years ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
Start date:
09/03/2016
Due date:
% Done:

0%

Feature Branch:
translate-server.git:master
Type of work:
Contributors documentation
Blueprint:
Starter:
Affected tool:

Description

We want to be able to redo this if necessary, so ideally we'd like to have a documented & tested setup process.

A great part of the setup is documented in Puppet: https://git-tails.immerda.ch/puppet-tails/tree/manifests/weblate.pp


Related issues

Duplicated by Tails - Bug #12333: Document translation platform Duplicate 03/13/2017
Blocked by Tails - Bug #13286: Review current documentation of the translation platform Resolved 06/30/2017

History

#1 Updated by BitingBird over 3 years ago

  • Status changed from New to Confirmed

#2 Updated by sajolida over 3 years ago

  • Category set to Infrastructure

#3 Updated by intrigeri about 3 years ago

  • Description updated (diff)

#4 Updated by emmapeel about 3 years ago

All the onfig files are at

/var/lib/weblate/config

The weblate code is installed from git at

/usr/local/share/weblate

#5 Updated by emmapeel about 3 years ago

  • QA Check set to Info Needed

shall I do this on the Translation platform blueprint?

I think it has valid information still about the requirements etc

Maybe I can Haz another blueprint? Could be [translate.tails.boum.org] or similar.

#6 Updated by intrigeri about 3 years ago

  • QA Check changed from Info Needed to Dev Needed

shall I do this on the Translation platform blueprint?

I say do that to start with. We can move stuff around later if/once someone has a better idea.

#7 Updated by emmapeel almost 3 years ago

  • Duplicated by Bug #12333: Document translation platform added

#8 Updated by emmapeel almost 3 years ago

Some information is already on the admins repo

#9 Updated by Anonymous almost 3 years ago

emmapeel wrote:

Some information is already on the admins repo

I'm not interested in the setup documentation but a documentation for weblate admins, let's say, for adding chinese or a new po file. How is that to be done? What part of the work happens automatically? What needs to be done manually, using which command?

#10 Updated by emmapeel almost 3 years ago

u wrote:

emmapeel wrote:

Some information is already on the admins repo

I'm not interested in the setup documentation but a documentation for weblate admins, let's say, for adding chinese or a new po file. How is that to be done? What part of the work happens automatically? What needs to be done manually, using which command?

That is exactly what comes in the translate-server repo to which you have access. It is meant for admin work, not only setup...

#11 Updated by Anonymous about 2 years ago

  • Target version set to Tails_3.6
  • Parent task changed from #11759 to #10034

#13 Updated by emmapeel about 2 years ago

  • Blocked by Bug #13286: Review current documentation of the translation platform added

#14 Updated by bertagaz almost 2 years ago

  • Target version changed from Tails_3.6 to Tails_3.7

#15 Updated by bertagaz almost 2 years ago

  • Target version changed from Tails_3.7 to Tails_3.8

#16 Updated by Anonymous over 1 year ago

  • Status changed from Confirmed to Resolved
  • QA Check deleted (Dev Needed)
  • Feature Branch set to translate-server.git:master

I've added a lot of documentation to this repository in order to reflect the current situation.

In the future: we do not want to intervene manually on the server anymore in order to add new languages. Instead this will happen like with anything new: create a branch locally, push and ask for review and merge.

Same goes for files from your personal staging website, we will not feed back anything manually to the Weblate repository. This will only be done by pulling and merging automatically from tails.git.

Same goes for the staging website, which will be built automatically every day.

I'll see what to do with the blueprint.
I now consider this ticket closed and will continue on #15085 and subtickets.

#17 Updated by Anonymous about 1 year ago

  • Parent task changed from #10034 to #15085

#18 Updated by intrigeri 8 months ago

  • Assignee deleted (emmapeel)

Also available in: Atom PDF