From f06752759b0cd911f24598e6319d0097044422dd Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Wed, 21 Mar 2018 18:11:02 -0700 Subject: [PATCH] Amend top-level project hosting spec This is an alternative way of handling the git hosting of top-level projects. This has advantages in that a new top-level site won't end up also serving unrelated (e.g., OpenStack) git repos, but it causes problems with the git:// protocol. Change-Id: Ieb7d09a9fcc2c6cb24b7dfc81f9dba0eebce50cf --- specs/project-hosting.rst | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/specs/project-hosting.rst b/specs/project-hosting.rst index 73bf70b..08d49e0 100644 --- a/specs/project-hosting.rst +++ b/specs/project-hosting.rst @@ -96,14 +96,16 @@ the CGIT_CONFIG env variable as appropriate, so that each domain displays only the relevant projects. Some new top-level projects may have code in OpenStack's Gerrit -already. To facilitate these cases, create symlinks on the git -servers so that every project can be cloned without it's prefix. We -could just do this as necessary for specific projects, however, this -is a likely step in the process of flattening the OpenStack git -namespace anyway, so we may as well solve the problem once globally. +already. To facilitate these cases, create a document root on the git +servers for each new top-level site, and create symlinks for these +projects. Set the Apache virtualhosts to these site roots, so that +the projects may be cloned via the symlink. The symlink may be +different than the name which appears in gerrit (eg, 'openstack/foo' +might simply be 'foo'). -This should work because we do, as a matter of policy, require unique -project names regardless of the prefix. +We will be unable to do the same for git-protocol hosting. Therefore, +we should not advertise any new git:// URLs, and should begin the +process of deprecating that protocol in favor of https. Websites --------