Changes
Page history
document gitolite repos migrations (
#41219
)
authored
Mar 20, 2024
by
anarcat
Show whitespace changes
Inline
Side-by-side
howto/git.md
View page @
65a42427
...
@@ -410,6 +410,28 @@ The following changes are done by the Fabric task:
...
@@ -410,6 +410,28 @@ The following changes are done by the Fabric task:
>
>
> Steps 4 and 5 would require GitLab API access.)
> Steps 4 and 5 would require GitLab API access.)
## Migration to other servers
Some repositories were found to be too sensitive for GitLab. While
some of the issues could be mitigated through
[
Git repository
integrity tricks
](
howto/gitlab#git-repository-integrity-solutions
)
, this was considered to be too time-consuming to
respect the migration deadline.
So a handful of repositories were migrated directly to the affected
servers. Those are:
-
DNS services, moved to
`nevii`
, in
`/srv/dns.torproject.org/repositories/`
*
`dns/auto-dns`
: DNS zones source used by LDAP server
*
`dns/dns-helpers`
: DNSSEC generator used on DNS master
*
`dns/domains`
: DNS zones source used by LDAP server
*
`dns/mini-nag`
: monitoring on DNS primary
-
Let's Encrypt, moved to
`nevii`
, in
`/srv/letsencrypt.torproject.org/repositories/`
*
`admin/letsencrypt-domains`
: TLS certificates generation
-
Monitoring, moved to
`nagios`
:
*
`tor-nagios`
: Icinga configuration
-
Passwords, moved to
`pauli`
:
*
`tor-passwords`
: password manager
## Destroying a repository
## Destroying a repository
Instead of migrating a repository to GitLab, you might want to simply
Instead of migrating a repository to GitLab, you might want to simply
...
...
...
...