Removed obsolete warning in README

This commit is contained in:
Rick Falkvinge
2016-04-04 03:27:51 +02:00
parent f7dcdeaea1
commit d86add121e
+1 -3
View File
@@ -35,9 +35,7 @@ Then, add the Swarmops repository to your list of software sources:
Then, run this to install the Swarmops frontend:
> `apt-get update; apt-get install 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.)
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.
If you installed onto a clean server, Swarmops will offer to configure Apache to use Swarmops as the default site. If you decline this offer, you can still enable the site by an `a2ensite swarmops` as a suggested configuration is provided. If you prefer to configure this entirely 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 continue installation from the running site.