moving Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 2.5 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 special actions. Note: Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user

moving Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 2.5 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 special actions. Note: Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user

up and moving Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 2.6 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 2.7 special actions. Note: Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the to users (if even allowed to see the repository URL at all). For example the GitHub URL with authentication added might look like: https:// user:your_access_token@github.com/WeblateOrg/weblate.git. Note:

up and moving Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 2.5 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 2.6 special actions. Note: Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user

up and moving Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 2.5 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 2.6 special actions. Note: Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user

up and moving Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 2.5 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 2.6 special actions. Note: Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user

up and moving Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 2.5 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 2.6 special actions. Note: Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user

up and moving Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 2.5 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 2.6 special actions. Note: Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user

Configuration instructions Weblate deployments Upgrading Weblate Backing up and moving Weblate Authentication Access control Translation projects Language definitions Continuous localization Licensing translations special actions. Note Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the to users (if even allowed to see the repository URL at all). For example the GitHub URL with authentication added might look like: https://user:your_access_token@github.com/WeblateOrg/web late.git. Note

Configuration instructions Weblate deployments Upgrading Weblate Backing up and moving Weblate Authentication Access control Translation projects Language definitions Continuous localization Licensing translations special actions. Note Depending on your setup, access to the Weblte repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the e.git), but for private repositories or for push URLs the setup is more complex and requires authentication. Accessing repositories from Hosted Weblate For Hosted Weblate there is a dedicated push user