Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
TPA team
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
TPA team
Wiki
Howto
git
Changes
Page history
New page
Templates
Clone repository
document gitolite repos migrations (
#41219
)
authored
9 months ago
by
anarcat
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
howto/git.md
+22
-0
22 additions, 0 deletions
howto/git.md
with
22 additions
and
0 deletions
howto/git.md
View page @
65a42427
...
...
@@ -410,6 +410,28 @@ The following changes are done by the Fabric task:
>
> 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
Instead of migrating a repository to GitLab, you might want to simply
...
...
This diff is collapsed.
Click to expand it.