However I prefer running commands to set up email accounts on Postfix and hosting multiple websites on Apache2. But I could not find;
/etc/apache2/sites-available/default ?
# ls /etc/apache2/sites-available/
Code:
apps.vhost ispconfig.conf ispconfig.vhost
Whether apps.vhost is default?
# cat /etc/apache2/sites-available/apps.vhost
Code:
######################################################
# This virtual host contains the configuration
# for the ISPConfig apps vhost
######################################################
Listen 8081
# NameVirtualHost *:8081
<VirtualHost _default_:8081>
ServerAdmin webmaster@localhost
<IfModule mod_php5.c>
DocumentRoot /srv/www/apps
AddType application/x-httpd-php .php
<Directory /srv/www/apps>
# php_admin_value open_basedir "/srv/www/apps:/usr/share:/tmp"
Options FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>
</IfModule>
<IfModule mod_fcgid.c>
DocumentRoot /srv/www/apps
SuexecUserGroup ispapps ispapps
<Directory /srv/www/apps>
Options Indexes FollowSymLinks MultiViews +ExecCGI
AllowOverride AuthConfig Indexes Limit Options FileInfo
AddHandler fcgid-script .php
FCGIWrapper /srv/www/php-fcgi-scripts/apps/.php-fcgi-starter .php
Order allow,deny
Allow from all
</Directory>
</IfModule>
ServerSignature Off
</VirtualHost>
It sounds like a bad idea to both run ispconfig AND configure your websites manually.
Now I haven't used Ispconfig myself, but since it is to take care of everything I seriously doubt you can just deit a few config-files and actually get it to work.
If you absolutely want to configure manually then I suggest you completely separate ispconfig's conf and your own.
That means, for your websites, add a vhost-file - do not edit the files ispconfig uses.
It sounds like a bad idea to both run ispconfig AND configure your websites manually.
Now I haven't used Ispconfig myself, but since it is to take care of everything I seriously doubt you can just deit a few config-files and actually get it to work.
If you absolutely want to configure manually then I suggest you completely separate ispconfig's conf and your own.
That means, for your websites, add a vhost-file - do not edit the files ispconfig uses.
Thanks.
This is a test. I'll use it learning ISPConfig.
But I couldn't resolve why going back to MSWindows age running GUI? We can config postfix, mysql etc on commands. What I'm interested is OpenVZ management. I'll install OpenVZ and create some clients for testing.
I haven't run OpenVZ at least 4 years knowing nothing about its latest development. Sharing kernel on clients saving lot of space additional to global update and upgrade. But at that time MSWindows couldn't run on it. How about now?
Sorry for late reply.
"why going back to MSWindows age running GUI" you ask - well, if you want something like ISPConfig then you want a GUI, why else use it?
If you want to configure everything on commands that's fine, what I mean is don't use ISPConfig and configure via commandline at the same time. This is because ISPConfig does more than just add entries in vhost-file etc, it keeps everything together to minimize the administrative burden.
You have to choose, use a GUI (=ISPConfig) or commandline.
Bookmarks