machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the confirmation message: GitHub repositories Access via SSH is possible override this in last step of component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the confirmation message: GitHub repositories Access via SSH is possible override this in last step of component configuration. Reasons to use this: Saves disk space on the server, the repository is stored just once. Makes the updates faster, only one repository is updated. There

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the confirmation message: GitHub repositories Access via SSH is possible override this in last step of component configuration. Reasons to use this: Saves disk space on the server, the repository is stored just once. Makes the updates faster, only one repository is updated. There

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the confirmation message: GitHub repositories Access via SSH is possible override this in last step of component configuration. Reasons to use this: Saves disk space on the server, the repository is stored just once. Makes the updates faster, only one repository is updated. There

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the confirmation message: GitHub repositories Access via SSH is possible override this in last step of component configuration. Reasons to use this: Saves disk space on the server, the repository is stored just once. Makes the updates faster, only one repository is updated. There

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the confirmation message: 90 Chapter 1. User docs The Weblate Manual override this in last step of component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the confirmation message: 90 Chapter 1. User docs The Weblate Manual override this in last step of component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the confirmation message: 90 Chapter 1. User docs The Weblate Manual override this in last step of component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: GitHub repositories in the last step of the component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 1.11. Version in the last step of the component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated