Trace:
no way to compare when less than two revisions

Warning: Undefined variable $user in /home/.sites/site2/wwwroot/web/lib/plugins/authpdo/auth.php on line 577

Warning: Undefined variable $user in /home/.sites/site2/wwwroot/web/lib/plugins/authpdo/auth.php on line 577

Warning: Undefined variable $user in /home/.sites/site2/wwwroot/web/lib/plugins/authpdo/auth.php on line 577

Differences

This shows you the differences between two versions of the page.


—userguide:vsite:template [2014/07/22 22:10] (current) – created chris@virtbiz.com
Line 1: Line 1:
 +======Add New Virtual Site ======
 +[[userguide:start|BlueOnyx]] > [[userguide:sitemanagement|Site Management]] > Template
 +
 +There are many advantages for setting defaults for the virtual sites. For example, since multiple sites can share an IP address, a default IP address can be set for all new virtual sites added. 
 +
 +The same is true for all of the options for a virtual site; it is best for you to decide the needs of your typical virtual site before assigning these values. Site defaults and site settings can only be configured by the Server Administrator.  If you (as the Server Administrator) enable services such as PHP or Shell Access the Site Administrators will automatically inherit those PHP settings and can enable or disable individual (per-user) shell access.
 +
 +When a template is configured, any sites that are subsequently created on the BlueOnyx server will default to the settings specified by the template.  Of course, those settings can be easily modified during or after a virtual site is created.  Changes made to the template will have no impact on sites that have already been provisioned on the server.
 +
 +===== Basic Settings: =====
 +
 +== IP Address: ==
 +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.
 +
 +== Host and Domain Name: ==
 +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.
 +
 +== Owner: ==
 +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.
 +
 +== Site Prefix: ==
 +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 bob@foo.com and bob@bar.net 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.
 +
 +== Web Server Aliases: ==
 +Enter additional host or domain names for which the virtual site should accept web requests. Separate multiple entries with commas or spaces.
 +  * Example: www2.example.com, www.example2.com. Note that DNS must be configured to resolve alias addresses in addition to the site name.
 +
 +== Web Alias Redirects: == 
 +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.
 +
 +== Disable Email for Domain: ==
 +Checking this box will disables the ability for the domain to receive emails.
 +
 +== Email Server Aliases: == 
 +Similar to Web Server Aliases, this allows the site to process requests for additional hostnames and/or domains.  
 +
 +== Catch-All Email Address: ==
 +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.
 +
 +== Maximum Allowed Disk Space: == 
 +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.
 +
 +== Maximum Allowed Number of Users: == 
 +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: == 
 +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.
 +
 +== Preview Site Configuration: ==
 +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).
 +  * SERVERNAME is the FQDN of your server.
 +  * vsitename is the FQDN of the site you are configuring.
 +
 +===== Services and Features: =====
 +
 +== Enable PHP Scripting: ==
 +Selections for PHP options that will apply to the virtual site:
 +  * Disabled: PHP will not be enabled for the site, and any PHP code will be displayed in a web browser as plain text.
 +  * Enable PHP Scripting:   PHP is enabled for the website.  
 +  * Enable SuPHP:  Enable the use of suPHP so that PHP scripts run with the UID of their owner. Be sure to configure a siteAdmin as owner of your /web folder through the Web Ownership menu! 
 +  * PLEASE NOTE: If suPHP is enabled, user owned webs are no longer supported and that feature will get turned off.
 +
 +== MySQL user and database: ==
 +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:
 +  * Username: Username of the MySQL user. Has rights and permissions only for the database specified below.
 +  * Password: MySQL password for the MySQL user in question.
 +  * Database Name: Name of the MySQL database for this site.
 +  * Database Host: Host on which the MySQL server is running. Typically this is localhost.
 +  * Port: Port on which the MySQL server is listening. Typically this is 3306.
 +
 +== Enable JSP and Servlets: ==
 +Enable to allow the use of JavaServer Pages (JSP) and Servlets.
 +**NOTE:** JavaServer Pages (JSP) is NOT the same as Javascript.   This is only for sites that will be serving JSP applets.  Do not check this box if you plan to use Javascript on your website.