Service/Weblate: Difference between revisions

(8 intermediate revisions by the same user not shown)

Line 65:

== Maintenance Notes ==

Weblate is maintained. (ibiam has step-up to be ~~maint~~)

Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;

{{Code|'''saslauthd -a shadow'''}}<br>

== Files ==

Line 84:

Line 87:

* Create new translation component in Weblate admin menu, ''Add new translation component'';

* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.

* Set version control system to ~~GitHub pull request~~.

* Set version control system to Git.

* Set source code repository link - using ~~https~~ -.

* Set source code repository link - using ssh -.

* Set repository branch.

* Set File format gettext PO file, File mask po/*.po

* Set Repository push URL to enable autoupdate of changes to Github from weblate.

* ~~Set~~ Push branch ~~to weblate-sync which~~ would be used ~~to create a PR~~.

* Leave Push branch empty as repository branch would be used.

* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.

* Check license in activity repo matches Translation license selected by weblate or set to the right license.

Line 95:

Line 98:

If an upload is incomplete, return to translation ~~componet~~, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

If an upload is incomplete, return to translation component, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the ~~Github pull request~~ version control above ~~and the Github configuration can be found in the~~

Weblate automatically pushes changes to Github when there's a change on weblate because of the Git version control above, the hooks configured in the repos make it easy for weblate to pull changes from Github.

~~environment file~~, the hooks configured in the repos make it easy for weblate to pull changes from Github.

== Backups ==

Weblate currently backs up to papert using [https://docs.weblate.org/en/weblate-5.4.2/admin/backup.html#remote-backups borgbackup] at {{Code|'''/home/weblate/backups'''}}.

You can view the list of backups with {{Code|'''borg list /home/weblate/backups'''}} which will ask for a passphrase,

the passphrase can be found in weblate admin page -> Backup -> Backup service credentials.

Borg's access is restricted to that directory.

== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

@@ Line 65: / Line 65: @@
 == Maintenance Notes ==
-Weblate is maintained. (ibiam has step-up to be maint)
+Weblate is maintained. (ibiam has step-up to be maintainer)
+After a restart, make sure to run saslauthd to enable authentication for postfix;
+{{Code|'''saslauthd -a shadow'''}}<br>
 == Files ==
@@ Line 84: / Line 87: @@
 * Create new translation component in Weblate admin menu, ''Add new translation component'';
 * Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
-* Set version control system to GitHub pull request.
+* Set version control system to Git.
-* Set source code repository link - using https -.
+* Set source code repository link - using ssh -.
 * Set repository branch.
 * Set File format gettext PO file, File mask po/*.po
 * Set Repository push URL to enable autoupdate of changes to Github from weblate.
-* Set Push branch to weblate-sync which would be used to create a PR.
+* Leave Push branch empty as repository branch would be used.
 * On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
 * Check license in activity repo matches Translation license selected by weblate or set to the right license.
@@ Line 95: / Line 98: @@
-If an upload is incomplete, return to translation componet, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.
+If an upload is incomplete, return to translation component, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.
 == Synchronization ==
-Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
+Weblate automatically pushes changes to Github when there's a change on weblate because of the Git version control above, the hooks configured in the repos make it easy for weblate to pull changes from Github.
-environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.
+== Backups ==
+Weblate currently backs up to papert using [https://docs.weblate.org/en/weblate-5.4.2/admin/backup.html#remote-backups borgbackup] at {{Code|'''/home/weblate/backups'''}}.
+You can view the list of backups with {{Code|'''borg list /home/weblate/backups'''}} which will ask for a passphrase,
+the passphrase can be found in weblate admin page -> Backup -> Backup service credentials.
+Borg's access is restricted to that directory.
 == References ==
 https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container