Our Redmine instance only hosts one project currently and there's no plan
to change that.

It does not work as I hoped and groente explained me how much extra work
this would require, which convinced me it's not worth it.

It can have surprising side-effects.

For some reason, Stdlib::Absolutepath thinks that '/' is not a valid
absolute path.

Removing one component from the web-visible path requires to re-add
the same component at the file system level.

Once the migration to redmine.tails.b.o is done, I'd like to drop the /code
URI path component by passing base_uri => '/', so we have URIs like:

  https://redmine.tails.boum.org/issues/15918

… instead of:

  https://redmine.tails.boum.org/code/issues/15918

Without this change, we would end up with things like:

  Alias "//plugin_assets"
         ^^

… that would be ugly and confusing, even if it might actually work.

We don't install it currently but let's ensure consistency in case
something pulls jetty9 some day.

snapshot.debian.org is currently unreliable for us.

This suite will be used for packages we need, but cannot pull from anywhere
else, in order to run PuppetDB from testing/sid on Stretch.

It's currently broken and yields large error messages (in HTML!)
when pushing to the canonical tails.git.

Users in the rsync_tails group should be allowed to modify files in there.