Difference between revisions of "SAC:Weblate"
| Line 25: | Line 25: | ||
Aside from general request, how you automate weblate use within your app depends on how you are hosted. | Aside from general request, how you automate weblate use within your app depends on how you are hosted. | ||
| − | The step generally includes | + | The step generally includes: |
| + | |||
1. Setting up a webhook in your project to notify weblate of changes: | 1. Setting up a webhook in your project to notify weblate of changes: | ||
| Line 32: | Line 33: | ||
** '''GitLab''' add in webhooks section of your project: https://weblate.osgeo.org/hooks/gitlab/ (you may specify filter of branches in branch config) | ** '''GitLab''' add in webhooks section of your project: https://weblate.osgeo.org/hooks/gitlab/ (you may specify filter of branches in branch config) | ||
| − | 2. Giving Weblate commit access | + | 2. Giving Weblate commit access (for direct commits) |
'''Gitea''' add [https://weblate.osgeo.org/keys/|weblates ssh pubkey ] as a deployment key in your gitea project | '''Gitea''' add [https://weblate.osgeo.org/keys/|weblates ssh pubkey ] as a deployment key in your gitea project | ||
Revision as of 09:23, 13 January 2022
Weblate is an instance of the Weblate server that runs in an LXD container in Osgeo9 and provides document translation servers for OSGeo community software. .
It can be accessed via https://weblate.osgeo.org/ (login with your OSGeo Userid)
Location and configuration
The application runs in LXD container called weblate on OSGeo9. It is run within that application using various docker containers launched with docker compose under the account weblate. Data is in a PostgreSQL database.
The configs are in /home/weblate/weblate-docker-compose
Administration
At the moment Regina Obe (creator of the container) and Sandro Santilli are admin users, although from the web UI this seems to provide no useful settings.
For maintenance and changes, administrators can access the container directly using
ssh ldap_account@osgeo9-weblate
Hosting your own project
Those who want to host their own project should put in a ticket in [Ticket] to be granted project creation permissions.
Aside from general request, how you automate weblate use within your app depends on how you are hosted. The step generally includes:
1. Setting up a webhook in your project to notify weblate of changes:
- Gitea add in webhooks section of your project: https://weblate.osgeo.org/hooks/gitea/ (you may specify filter of branches in branch config)
- Github add in webhooks section of your project: https://weblate.osgeo.org/hooks/github/ (you may specify filter of branches in branch config)
- GitLab add in webhooks section of your project: https://weblate.osgeo.org/hooks/gitlab/ (you may specify filter of branches in branch config)
2. Giving Weblate commit access (for direct commits)
Gitea add ssh pubkey as a deployment key in your gitea project Github Invite the osgeoweblate github account to your project. Gitlab TBD