From a821d06da2da2f3e3f4ea3216c5b6809dcf742f1 Mon Sep 17 00:00:00 2001 From: Rick Falkvinge Date: Mon, 21 Mar 2016 09:31:29 +0100 Subject: [PATCH] Updated install instructions to reflect autoconfig --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2a41799a..b0f1203d 100644 --- a/README.md +++ b/README.md @@ -37,9 +37,9 @@ Then, run this to install the Swarmops frontend: (the install sometimes hangs on installing a dependent package, apache2-mod-mono, right after the message _apache2_invoke: Enable module_mod_mono_. That's not an issue with Swarmops, but still irritating. It manifests as Apache trying to restart ("Restarting web server apache2...") and freezing there. This irritating bug in the apache2-mod-mono install can be released by opening a second shell and restarting Apache using `/etc/init.d/apache2 restart` in the second shell, at which point the install in the first shell will continue.) -Install a new Virtual Host in Apache, a Mono host, pointing at /usr/share/swarmops/frontend as its directory. We're using /usr/bin/mod-mono-server4 as our server. Note the 4 at the end; many configurators are old and will set a 2 there. +If you installed onto a clean server, Swarmops will offer to configure Apache to use Swarmops as the default site. If you prefer to configure this manually, install a new Virtual Host in Apache, a Mono host, pointing at /usr/share/swarmops/frontend as its directory. We're using /usr/bin/mod-mono-server4 as our server. Note the 4 at the end; many configurators are old and will set a 2 there. See /etc/apache2/sites-available/swarmops.conf for a template file. -Navigate to the new site and configure from there. +Navigate to the new site and continue installation from the running site. Once configured and logged in, you may also want to install