New virtual sites are added via the Add Site page. Certain information is required in order to configure a new site on the BlueOnyx server.
This is the IP address that you wish to assign to the new site. It should be an IP address that is already configured on your server, or is available for your user from your network administrator or ISP. If you add an IP address here that was not already configured on the server, BlueOnyx will automatically add the new IP address to the network configuration.
A host name is the first part of a fully-qualified domain name (FQDN). For example, mail and www are valid host names. A domain name is the second part of a FQDN. For example, example.com and BlueOnyx.org are valid domain names.
By default, new sites are owned by “admin”, the main server administrator. If you have configured additional server administrators and the new site should be under another administrator's control, you may select that administrator from the pull-down menu.
The Site Prefix is an optional prefix that allows you to identify users or services related to a site. If set, all (newly created) usernames will be prefixed with this string. A prefix must be alphanumeric (numbers and/or letters only) and may not be longer than five characters. This is helpful when you plan to host many domains on a server, and users may wish to use similar usernames. For instance, you may host two sites (foo.com and bar.net), each with a user who wishes for the username “bob”. Without a site prefex, only one user can be “bob”. By setting a site prefix (foo, bar) the “bob” in foo.com becomes foo-bob and the “bob” in bar.net becomes bar-bob. Actual email delivery and addressing will remain email@example.com and firstname.lastname@example.org through email aliasing in User Management. Please note: A prefix can be added or changed at a later time. But doing so will NOT affect any usernames that are already present.
Enter additional host or domain names for which the virtual site should accept web requests. Separate multiple entries with commas or spaces.
If a site has multiple Web Server Aliases, then two kinds of behaviors are possible: (a) A URL request to a Web Server Alias URL will redirect to the main sites URL. ie: If a request is made for foo.com, the BlueOnyx server will automatically re-write as www.foo.com. This is the default. (b) AnURL request to a Web Server Alias will not redirect to the main sites URL. Instead the alias will look like an independent site on its own. Either foo.com or www.foo.com will appear in the address bar. Please note that this behaviour can be troublesome with web statistics and/or certain CMS systems.
Checking this box will disables the ability for the domain to receive emails.
Similar to Web Server Aliases, this allows the site to process requests for additional hostnames and/or domains.
Specify an email address to receive messages that are addressed to unknown users and mailing lists. If left blank, email addressed to unknown users or mailing lists will not be accepted. If the specified address does not exist, email addressed to unknown users and mailing lists may be rejected as invalid. CAUTION: using this option will most likely result in a massive increase in spam received.
The maximum amount of disk space quota that the site will be allowed to use. This quota includes all files belonging to the site's users, stored logfiles and email. Once the maximum quota has been reached, no new files or emails can be stored. The quota can be modified at a later date.
The maximum number of users that may be configured for the site. Users have access to email, and if specified, FTP and shell.
Automatic DNS configuration manages DNS records for this site. Web and Email server aliases are supported only if they share the site domain name. This service does not register the domain name with a top level registrar.
If the Preview Site Configuration box is checked, the website may be previewed in the browser by browsing to http://SERVERNAME/vsitename/ (with the trailing slash).
Selections for PHP options that will apply to the virtual site:
Allows you to automatically create or remove a MySQL database and a MySQL user for this site. PLEASE NOTE: If the checkbox is already checked, then unchecking it and saving the changes will remove the MySQL database AND the user.
Clicking the checkbox to enable MySQL service on the site will inflate a sub-window with the following inputs:
Enable the use of CGI applications.
Enable the use of Server-Side Includes (SSI)
Enable SSL to allow secure access to the web server for the site.
== Bandwidth Limits = Limit the maximum data transfer rate from sites.
If enabled, then each user has his own webspace, which is separated from<br>the main website webspace and reachable through http://www.example.com/~username/ . Users can then upload their own webpages through FTP into their own /web directory. PLEASE NOTE: If suPHP is enabled, user owned webs are no longer supported and this feature will be turned off.
Users who are SiteAdministrators can allways FTP to the server - as long as the FTP service in general is enabled. If you also want to allow regular users to access their filespace by FTP, then tick this box.
Enable anonymous FTP service for the site.
Enable shell access to allow the creation of users who can connect to the server using services such as telnet and ssh.
Allows you to enable Sub Domains for virtual hosts and specify the maximum number of subdomains.