Difference between revisions of "SAC:Weblate"
| (4 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
For maintenance and changes, administrators can access the container directly using | For maintenance and changes, administrators can access the container directly using | ||
| − | ssh | + | ssh '''ldap_account'''@osgeo7-weblate |
| − | |||
= Hosting your own project = | = Hosting your own project = | ||
| Line 26: | 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 33: | 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. You can have weblate push changes to your repo in one of two ways |
| + | |||
| + | Directly or via Pull requests | ||
| + | |||
| + | a) Directly Giving Weblate commit access (for direct commits) | ||
| + | In the https://weblate.osgeo.org/settings/<your-project>/<main-component>/#vcs (replace <your-project> <your-component> with your specifics) choose '''Git''' for '''Version Control System''' | ||
| + | |||
| + | ** '''Gitea''' add [https://weblate.osgeo.org/keys/|weblates ssh pubkey ] as a deployment key in your gitea project | ||
| + | ** '''Github''' Invite the [https://github.com/osgeoweblate osgeoweblate] github account to your project. | ||
| + | ** '''Gitlab''' TBD | ||
| + | |||
| + | or | ||
| + | |||
| + | b) via pull requests | ||
| + | In the https://weblate.osgeo.org/settings/<your-project>/<main-component>/#vcs (replace <your-project> <your-component> with your specifics) choose | ||
| + | |||
| + | ** '''Gitea''' choose '''Gitea Pull Request''' for '''Version Control System''' # currently this doesn't work | ||
| + | ** '''Github''' choose '''Github Pull Request''' for '''Version Control System''' - in this model weblate creates a fork of your project under https://github.com/osgeoweblate and will create pull requests against your project with that fork | ||
| + | ** '''Gitlab''' choose '''Gitlab Merge Request''' for '''Version Control System''' # not tested | ||
| − | |||
| − | |||
| − | |||
[[Category:Infrastructure]] | [[Category:Infrastructure]] | ||
[[Category:Services]] | [[Category:Services]] | ||
Latest revision as of 05:46, 27 September 2023
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@osgeo7-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. You can have weblate push changes to your repo in one of two ways
Directly or via Pull requests
a) Directly Giving Weblate commit access (for direct commits) In the https://weblate.osgeo.org/settings/<your-project>/<main-component>/#vcs (replace <your-project> <your-component> with your specifics) choose Git for Version Control System
- Gitea add ssh pubkey as a deployment key in your gitea project
- Github Invite the osgeoweblate github account to your project.
- Gitlab TBD
or
b) via pull requests In the https://weblate.osgeo.org/settings/<your-project>/<main-component>/#vcs (replace <your-project> <your-component> with your specifics) choose
- Gitea choose Gitea Pull Request for Version Control System # currently this doesn't work
- Github choose Github Pull Request for Version Control System - in this model weblate creates a fork of your project under https://github.com/osgeoweblate and will create pull requests against your project with that fork
- Gitlab choose Gitlab Merge Request for Version Control System # not tested