Feature #11760

Document the entire weblate installation & setup process

Added by Anonymous 2016-09-03 04:26:09 . Updated 2019-06-27 17:16:59 .

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

0%

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

Starter:
Affected tool:
Deliverable for:
309

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

Subtasks

Related issues

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

History

#1 Updated by BitingBird 2016-10-16 05:22:15

  • Status changed from New to Confirmed

#2 Updated by sajolida 2016-11-04 12:20:58

  • Category set to Infrastructure

#3 Updated by intrigeri 2017-02-11 17:05:13

  • Description updated

#4 Updated by emmapeel 2017-02-11 22:30:03

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 2017-02-13 17:00:05

  • 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 2017-02-14 13:33:50

  • 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 2017-03-14 08:25:15

  • has duplicate Bug #12333: Document translation platform added

#8 Updated by emmapeel 2017-03-14 08:26:06

Some information is already on the admins repo

#9 Updated by Anonymous 2017-03-14 08:56:54

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 2017-03-14 09:04:27

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 2017-12-19 12:13:10

#12 Updated by Anonymous 2017-12-19 12:14:05

  • Deliverable for set to Sponsor_L

#13 Updated by emmapeel 2018-01-31 17:52:50

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

#14 Updated by bertagaz 2018-03-14 11:32:08

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

#15 Updated by bertagaz 2018-05-10 11:09:05

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

#16 Updated by Anonymous 2018-06-12 14:22:43

  • 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 Feature #15085 and subtickets.

#17 Updated by Anonymous 2019-02-07 15:37:49

#18 Updated by intrigeri 2019-06-27 17:16:59

  • Assignee deleted (emmapeel)