Weblate.duniter.org improvement

Tools
,
1

Hi!

I wonder if, to be more agile, weblate.duniter.org could have 1-2 more users who can receive and accept/deny new translation projects at our Weblate instance, and then create the new project. Specially I’d like @Moul , @kapis , @vjrj to be one of them :wink: (any other senior and active community member could also apply!).

I’m not sure if it’s possible, but I suppose web can use a not “root” role with this permission. Any of you have experience with it? If not, I can search about it :-p

2

@arbocenc Your Weblate instance is broken!

3

Thanks for the warning… Going there!

4

Solved! Try again!

5

I see weblate.duniter.org is one major version late (V4 and note V5).
Is there an issue about updating ?

I will add tools / g1vote-view · GitLab for translation review soon, and perhaps tools / multilang-mnemonic-converter · GitLab

6

Here you are: Funcionalitat/Millora #2254: Actualitzar a una nova versió - Weblate Duniter - Calbasi.net: gestor de projectes

I’ve no experience upgrading weblate. Any advices? Is it an easy process?

7

I don’t know, the most important thing in my opinion is : is there recent backup ?
So if it don’t go smooth, we can rollback without harm.

8

Yes, there are daily backups.

9

I was translating Cesium2 to Portuguese yesterday, but suddenly I got this error today.

image
image1066×581 60.2 KB

10

@arbocenc same for me today: site is down !

11

cc @vit Thanks for reporting… Just trying to fix it!

12

Just restarting the weblate instance do the trick. Try now

13

Je suis heureux de voir le site fonctionner à nouveau. Mais quel dommage qu’il n’ait pas gardé et j’aie perdu tout mon travail de traduction de Cesium2 vers le Portugais

14

Are you sure?? I’ve not use any backup, so your work should stay there. When do you work on the Portuguese translation for last time?

15

@arbocenc
On the Weblate instance, the component currently pushes to GitLab using a SSH key. I would like to switch to GitLab Merge Requests instead.

Could you please do the following on the Weblate server?

1. Remove the SSH key

  • Delete the private key file used by Weblate in DATA_DIR/ssh/ (typically id_rsa or id_ed25519).

2. Add the GitLab API credentials
In the Weblate server configuration (settings.py or environment variables), add:

GITLAB_CREDENTIALS = {
    "gitlab.com": {
        "username": "<gitlab-username>",
        "token": "<gitlab-api-token>",
    }
}

I will provide the username and token separately by PM.

3. Change the component VCS backend (already done in Tikka project)
In the component settings, switch the Version control system from Git to GitLab merge requests, and use the HTTPS repository URL.

Once this is done, Weblate will open Merge Requests instead of pushing directly to main.

Thanks a lot for your help.
[EDIT]
dont do anything! Just help me investigate why weblate can add commit in my gitlab protected main branch. Thx !

16

Should we do that for all projects that use the weblate? Like Cesium for example?

17

Sorry, I made a mistake in understanding how weblate could add commits on my tikka protected main branch reserved only to maintainer level accounts. I didn’t allow the public ssh key of weblate server to access my gitlab account. So I will continue to investigate how weblate do to access my protected main branch…

[EDIT]
Found ! A weblate user had Maintenance Rights on my repo and could push on protected branches! I reduced the level to Developer. Everybody should check the level of permissions of this user on his repo (@moul look at the default level of this user…) .


Weblate push user
@weblate