Apache2 config port isses

[Andrew Ruthven]

If Apache2 is configured to use both HTTP and HTTPS then installing mahara-apache2 (for Debian) breaks the Apache2
setup.

The virtual host for mahara needs to specify the port to listen on.

If the system admin fixes this, then the next time mahara-apache2 is upgraded the fix is lost as the Apache2 config
file is generated from a template so the local customisation is lost.

This bug was imported from eduforge.org, see:
https://eduforge.org/tracker/index.php?func=detail&aid=639&group_id=176&atid=739

[Nigel-catalyst (nigel-catalyst)]

23:45 <Ned> basically, the simplist way to solve it is ...
23:45 <Ned> make a new apache conf
23:45 <Ned> check it in
23:45 <Ned> get debian to deploy it into sites-available
23:45 <Ned> and leave it at that

(typo-edited chatlog detailing what should be done to fix this)

[Nigel-catalyst (nigel-catalyst)]

Raising priority (and taking from Martyn who has little to do with this now). Francois is fixing our debian packaging, I might complete his work later if he doesn't.

[Nigel-catalyst (nigel-catalyst)]

Peterb also wants the cron logs to go to /var/log/mahara/cron.log

[Nigel-catalyst (nigel-catalyst)]

Francois has done lots of work on the debian package recently, in order to fix this and other problems.

I have moved the cron log to /var/log/mahara.

[Andrew Ruthven (andrew-etc)]

In 0.9.0 the Apache2 config file handling is much better, thank you. But it will still break a system with other virtual hosts using SSL. This isn't a nice user experience.

I suggest that the config file get installed in to /etc/apache2/sites-available (not /etc/apache2/conf.d) and a debconf question is used to optionally use a2ensite to enabled it. With some suitable warning about potential breakage.

This allows the admin to modify the config file before possibly breaking things. It also satisfies the requirement of Nigel and Martyn of being able to get a running mahara install by just using apt-get install.

[Nigel-catalyst (nigel-catalyst)]

Francois - your thoughts on Andrew's comments?

[François Marier (fmarier)]

We decided to split up the debconf answers from the rest of the config file so that admins could customize the file we provide in /etc/apache2/conf.d. So these customizations will not be overwritten.

Now, if the config file we ship breaks apache once Mahara is installed, then, you're right, we should fix that. If specifying the port (by default, 80) fixes that problem, then that's probably the quickest way to solve the problem for now.

The solution that Andrew proposed (sites-available + debconf question about running a2ensite) sounds good too. I don't have much time right now to make that change and test it, but feel free to try it out, it's in git ;-)

[Nigel-catalyst (nigel-catalyst)]

We have moved the debian side of things to debian itself. We will do etch packages as backports at some point.

[Nigel-catalyst (nigel-catalyst)]

I had a quick look at the instructions for getting a package into backports. I think there's two points that mean we shouldn't bother with a backport:

1. Please only upload package with a noteable userbase. User request for the package maybe an indicator.
2. Reconsider if the package can be installed directly from testing without any recompilation and handled via pinning

The packaging installs on etch fine, and if it doesn't that should be considered a bug.

Which means there's nothing more to do for this.