Simplifying hosting services (aka "breaking up the monolith")

[Stelian Ionescu]

[...]
> In order to simplify our setup (and eliminate the deployment problems
> we're experiencing) and at the same time add support for requests like
> those from Marco who wants to be able to deploy sites for multiple
> projects under the same umbrella, I've decided I want to move
> projects' sites to their own (sub)domains. In the past I thought this
> would need to be subdomains along the lines of
> https://<project>.project.common-lisp.net/. Although that's a
> deployment model that would work with GitLab Pages, I've decided
> against it. I'll move the hosted projects to:
>
>    https://<project>.common-lisp.dev/
>
> (I acquired common-lisp.dev for this purpose this morning.)

Very good idea, especially for security considerations: it's better that user-generated content be hosted under a different TLD.

> The setup I'm proposing is that we have a good look at the tons of
> rewrite rules we have currently in place and clean up the rewrite
> rules that we don't need anymore. Then, we create rewrite rules for
> the current project namespaces at
> https://common-lisp.net/project/<project>/ to map to
> https://<project>.common-lisp.dev/. There are a few projects which
> aren't using GitLab Pages to deploy their websites yet, mostly because
> they have no active maintainers. These projects will keep being served
> from their current locations on the filesystem of the common-lisp.net
> host, but their content will be available through the new
> <project>.common-lisp.dev URL space.

+1

-- 
Stelian Ionescu