Merge "Amend top-level project hosting spec"

This commit is contained in:
Zuul 2018-04-03 20:25:26 +00:00 committed by Gerrit Code Review
commit 05e7fe2f17

View File

@ -96,14 +96,16 @@ the CGIT_CONFIG env variable as appropriate, so that each domain
displays only the relevant projects. displays only the relevant projects.
Some new top-level projects may have code in OpenStack's Gerrit Some new top-level projects may have code in OpenStack's Gerrit
already. To facilitate these cases, create symlinks on the git already. To facilitate these cases, create a document root on the git
servers so that every project can be cloned without it's prefix. We servers for each new top-level site, and create symlinks for these
could just do this as necessary for specific projects, however, this projects. Set the Apache virtualhosts to these site roots, so that
is a likely step in the process of flattening the OpenStack git the projects may be cloned via the symlink. The symlink may be
namespace anyway, so we may as well solve the problem once globally. 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 We will be unable to do the same for git-protocol hosting. Therefore,
project names regardless of the prefix. we should not advertise any new git:// URLs, and should begin the
process of deprecating that protocol in favor of https.
Websites Websites
-------- --------