[sysconfig] Stuff ssh config into "empty" global config

This is an ugly hack. The "no sysconfig" runmode option
creates an obvious problem if an ssh config exists: It
won't be provisioned to the client, so it's not reachable
via ssh. We need a proper mechanism for managing config,
that flags modules by whether they should be ignored for
"no sysconfig" runmode or not, and while we're at it,
make it possible to assign additional modules to rooms.

1 files changed, 1 insertions, 1 deletions

diff --git a/modules-available/sysconfig/api.inc.php b/modules-available/sysconfig/api.inc.php
index 9d621e5c..bb2d9f5e 100644
--- a/modules-available/sysconfig/api.inc.php
+++ b/modules-available/sysconfig/api.inc.php
@@ -32,7 +32,7 @@ if (Module::isAvailable('runmode')) {
 	}
 }
 if ($runmode !== false && $runmode->noSysconfig && file_exists(SysConfig::GLOBAL_MINIMAL_CONFIG)) {
-	$row = array('filepath' => SysConfig::GLOBAL_MINIMAL_CONFIG);
+	$row = array('filepath' => SysConfig::GLOBAL_MINIMAL_CONFIG, 'title' => 'config');
 } else {
 	$locationId = false;
 	if (Module::isAvailable('locations')) {