| This manual is deprecated. Please visit https://groupoffice.readthedocs.io for the latest documentation. |
Difference between revisions of "Server Manager"
| Line 13: | Line 13: | ||
You should not have to edit any of these configuration files. Everything can be managed through the servermanager. This is just to explain how it works. | You should not have to edit any of these configuration files. Everything can be managed through the servermanager. This is just to explain how it works. | ||
| − | A virtual host for all Group-Office installations is created in: | + | A virtual host for all Group-Office installations is created in: <b>/etc/apache2/sites-enabled/000-groupoffice.</b> |
| − | + | ||
| − | <b>/etc/apache2/sites-enabled/000-groupoffice.</b> | + | |
It uses a VirtualDocumentRoot (More info: http://httpd.apache.org/docs/2.0/mod/mod_vhost_alias.html) so any domain name pointing to the server IP will automatically work when it's created in the servermanager. | It uses a VirtualDocumentRoot (More info: http://httpd.apache.org/docs/2.0/mod/mod_vhost_alias.html) so any domain name pointing to the server IP will automatically work when it's created in the servermanager. | ||
SSL is also preconfigured with a test certificate using the apache module mod_ssl. | SSL is also preconfigured with a test certificate using the apache module mod_ssl. | ||
| − | The VirtualDocumentRoot is located at <b>/var/www/groupoffice/</b>. There's a directory for each domain in that directory. For example: | + | The VirtualDocumentRoot is located at <b>/var/www/groupoffice/</b>. There's a directory for each domain in that directory. For example: /var/www/groupoffice/customer.groupoffice.eu/ |
| − | + | ||
| − | + | ||
In that directory there is a symlink called "groupoffice" that points to <b>"/usr/local/groupoffice"</b>. That is where the actual source of Group-Office is located. | In that directory there is a symlink called "groupoffice" that points to <b>"/usr/local/groupoffice"</b>. That is where the actual source of Group-Office is located. | ||
Revision as of 14:50, 4 February 2009
Contents
Server manager
The server manager is a module that can manage other Group-Office installations on a Debian server. Partners can obtain the installation package from Intermesh.
You need to have a domain and all subdomains point to the IP address of the server. For example *.groupoffice.eu. CustomerX will get the domain http://customerx.groupoffice.eu
By default the servermanager is installed at https://<IP_ADDRESS>/
How is the server organized?
The server uses Apache 2, Postfix, Dovecot and Spamassassin
Apache and Group-Office
You should not have to edit any of these configuration files. Everything can be managed through the servermanager. This is just to explain how it works.
A virtual host for all Group-Office installations is created in: /etc/apache2/sites-enabled/000-groupoffice.
It uses a VirtualDocumentRoot (More info: http://httpd.apache.org/docs/2.0/mod/mod_vhost_alias.html) so any domain name pointing to the server IP will automatically work when it's created in the servermanager. SSL is also preconfigured with a test certificate using the apache module mod_ssl.
The VirtualDocumentRoot is located at /var/www/groupoffice/. There's a directory for each domain in that directory. For example: /var/www/groupoffice/customer.groupoffice.eu/
In that directory there is a symlink called "groupoffice" that points to "/usr/local/groupoffice". That is where the actual source of Group-Office is located. There is also a folder called "/usr/local/servermanager". This is the Group-Office source that also contains the servermanager module and the postfixadmin module.
The config.php file for each Group-Office installation can be found in "/etc/groupoffice/<DOMAIN>/config.php". There is also a "/etc/groupoffice/globalconfig.php". The configuration parameters in here apply to all installations.
There is also a configuration file for the servermanager module: "/etc/groupoffice/servermanager/config.inc.php". It contains some default configuration values for new installations.
Postfix and Dovecot
Postfix is setup to use virtual accounts in MySQL. Very similar to this approach:
http://www.howtoforge.com/postfix_mysql_dovecot_dspam_clamav_postgrey_rbl_debian_etch
But I didn't use the VDA patch and used spamassassin.
All users are stored in the MySQL database "servermanager" and can be managed with the servermanager. A special perl script is used to handle autoresponse when a user is on vacation. Dovecot checks the quota in MySQL.
The actual mails are stored in /vmail/<domain>/<user>/
Backup the server
To be able to restore the servermanager completely you need to backup the following folders:
/var/www : The files stored in Group-Office /vmail : The e-mail messages /etc/groupoffice : The configurations
A backup from all MySQL databases should also be made
A server can be restored by reinstalling Debian and the Group-Office servermanager. After that you can restore the folders and databases.
