YES Linux Forum

Hi ,

I'm just a visitor and during my google searches I found your site. I don't really understand what YES Linux is but now I see in this changelog that it is related to VirtualHost's, I'm interested in YES Linux.

Is YES Linux made to be an ISP (mass websites hosting, mass e-mails hosting etc...) ?

I would like to know how are the VirtualHost's managed :

:arrow: Do you use mode_perl to create the VirtualHost's in the Apache conf, taking the parameters of each in a database ? (when you update the database, you just have to reload Apache)

or

:arrow: Do you use mod_perl to dynamically choose the document_root for the requested host (taking the infos of the corresponding document_root in a database) using PerlTransHandler ? *

or

:arrow: Do you use mod_vhost_dbi that does the same thing as above ? *

:arrow: Do you use any other method ? In this case I'm really interested in how you do, especially if you dynamically create the VirtualHost, and more especially if you have can manage dynamically all the directives a VirtualHost can have (but just ServerAlias should be useless)

* The problem of these method is you can't have all the directives of a VirtualHost so for example you can't modify the CustomLog. I made many many seaches to know how to change CustomLog dynamically without having to reload Apache to load the VirtualHost's that consumes many ram MB's.

Furthermore, I saw you are planning to make statistics for each VirtualHost, so you have one individual log for each VirtualHost, I'd mike to know how you do ?

Thank you a lot in advance and congratulations for YES Linux although I didn't download it nor the sources 8).

Currently YES Linux is not made for the ISP Market, but in the future there will be a version more targeted for an ISP of a SOHO.  That said YES Linux can be used by an ISP, it just isn't made for that function currently.    With the Virtual Hosting support YES Linux provides there are users that are using it to provide web hosting capabilities.

In YES Linux 2.1.2 we provide both WWW and Email Virtual Hosting, and Statistics on each virtual host and mail server.

We accomplish the WWW Virtual Hosting configuration using the Apache 2 feature of configuration fragments.  The user interface uses php to drive the process, each fragment is created using the YES Linux configuration system which is a wrapper around Apache Ant.  YES Linux is designed so the any administration application will work with it.  There are users that use Webmin, others that use CPanel, or our Administration Application.  To YES Linux it doesn't matter.  All YES Linux webserver additions use the Apache 2 fragment frature.  Currently we don't support modifing all the directives form the web interface although we would like to.

Because we use fragments each virtual host has its own logs and area, thus every site is independant of the other.

The email system uses Postfix, Courrier-Imap and Postgresql.  So all accounts are virutal and are stored in postgres.  Again the administration of the accounts is done using php, so you can scale as large as you hardware allows.  Postfix is configured to only allow SMTP-Auth connections and uses online spam databases.  The email system is able to use imaps, pops, and smtps if that is needed.

For more information please look at the docs http://www.yeslinux.org/docs.php look at the WebSite Administration and Email Administration.

The previous reply is from me*

Ok I understand, thank you .