* It can now work on individual domains specified on the cmd line.
* Domains will be re-enabled if disabled, if they've been mentiond on
  the command line.
* Verbose output gives more of a clue to what is going on.
* Manpage has been updated.

This allows a single domain's config to be overridden/reset using
--force.

This generalises a fix for the problem described in
https://projects.bytemark.co.uk/issues/12783

Always re-create missing links in sites-enabled

https://projects.bytemark.co.uk/issues/12768

See merge request !3

Exit if no domains have been detected

See https://projects.bytemark.co.uk/issues/12783

It seems that during periods of memory pressure, sometimes `getpwuid` fails and `symbiosis/domains.rb` just dies mid-script. Nothing is returned to `symbiosis-httpd-configure`, so the `configurations` array remains empty indicating that there aren't any domains configured. All sites in `sites-enabled` subsequently get deleted.

The only situation in which the `configurations` array should be empty is when `/srv` has no directories, but in that case there's no real reason to run `symbiosis-httpd-configure`. As I understand it, every customer using Symbiosis+Apache should have at least one directory in `/srv`, so it's probably better to just exit if `configurations` is empty rather than continue to delete all sites.

See merge request !4

* confirmation of verification
* confirmation of new SSL certificate set

This is to beat the LetsEncrypt renewal notice at 19 days.

Also --force now implies --verbose.

We no longer log errors during the normal course of events, such
as:

* Virtual Hosts that don't exist.
* Malformed input-lines.

Add -v, or --verbose, to see them.

This is better than using a path.

We've moved the opening of the logfiles into a central routine,
such that we can add some sanity checking, and ensure that we're
not going to append to files which are symlinks.

As part of this work we've also made the --max-files|-f command-line
argument function, with a default of 100.  When more than the specified
number of logfiles are open they are all closed so they can slowly
re-grow.

Supply absolute path of temporary exim config file

Remove 'restart exim' part of header

Fix comment

This is required, and achieved via a symlink

Some versions use:

dh_prep
dh_auto_install
dh_install

Some use:

dh_build
dh_binary

The former will work.  The latter will clean debian/tmp as part of
the process, which means installing the binary to debian/tmp will
fail.

I tested this too.

This code is functionally identical to the Ruby version, all being
well, and barring bugs.

The intention is that we can allow users to install this package
if they're at all suffering with issues with RAM usage.  This is
deliberately taken as a safe middle-ground before rewriting a core
component of symbiosis and forcing all users to upgrade at once.

Once this package is installed the old ruby-based logger will be
divered, via dpkg-divert, such that it is no longer in use and
can be replaced.

Removign this package undoes the diversion to restore the system
to that state it was previously in.

This updates #12663.

email: futher fix to makefile to make tests pass



See merge request !2

email: Makefile fix for patched exim4



See merge request !1