InterWorx-CP is divided into two main tools: NodeWorx and SiteWorx. NodeWorx is the server administrator and reseller interface, and SiteWorx is the website administrator interface.
When the server administrator or reseller wants to create a website, they create a "SiteWorx Account". Each SiteWorx account is mapped to an IP and a unique Linux user on the server. A SiteWorx account is permitted to have multiple domains. SiteWorx allows users to manage their files on the server, manage email accounts, manage databases, etc. Even some more technically-minded tools are available like setting CRON jobs for the Linux user and viewing Apache transfer and error logs Access to features and the number of databases/email accounts can be restricted when creating the SiteWorx account.
Siteworx accounts are accessed via
https://domain.com:2443/siteworx. If DNS is not yet setup one can use the server's IP to access the interface. From the NodeWorx interface, the server administrator or reseller can jump directly to a SiteWorx account and bypass authentication.
Below are the options you can set for a SiteWorx to limit the amount of resources a SiteWorx user can use or the options they have access to.
This is the domain that you wish your SiteWorx account to have.
Note: The domain name should be entered WITHOUT the 'www' prefix. The 'www' prefix will be properly dealt with by the underlying system.
This drop-down list displays a list of available IP addresses that can be assigned to the new SiteWorx account. This will be the IP Address used by this domain.
This is the day of each month that the billing cycle starts. This affects when bandwidth counters reset each month. If you set your billing day to 12, this means that on the 12th of every month, a new bandwidth monitoring period will start for this account.
The *nix user the SiteWorx account's content will be owned by. By default this is generated by the control panel based on domain name. You can elect to change it if you dislike what the control panel has chosen.
This is the name that will appear in the list of SiteWorx accounts. This field is optional.
The e-mail address of the SiteWorx account holder that is used for the SiteWorx login. This will also be used as a point of contact for the account.
The password the account owner uses to login to SiteWorx.
The language used by the account owner in SiteWorx.
The theme used by the account owner in SiteWorx.
The maximum amount of storage in megabytes allowed for this account. It is enforced by the Linux quota system and thus in order for the entire impact to disk space to be measured, /chroot, /home, and /var must all be mounted on the same partition.
The maximum amount of bandwidth in gigabytes allowed per month. Includes FTP bandwidth usage.
The number of e-mail aliases (often called e-mail forwards) allowed for this account. Aliases are a "virtual" email address that just redirects all mail to another address.
The number of e-mail autoresponders (often called robots) allowed for this account.
The number of POP3/IMAP/Webmail e-mail boxes allowed for this package.
The number of group e-mail addresses allowed for this account. A group e-mail address an alias that sends to multiple recipients.
The number of FTP accounts allowed for this account.
The number of MySQL databases allowed for this account.
The number of MySQL users allowed for this account.
The number of domains that can be pointed to this domain. A pointer domain can also be referred to as a "parked" domain. A pointer domain is a domain that redirects to a specified domain. For example, if you register bedangerous.com, bedangerous.net, and bedangerous.org, you can "point" (redirect) traffic for bedangerous.net and bedangerous.org to bedangerous.com.
The number of secondary domains that can be added to this account. Secondary domains share all the package feature limits (e-mail boxes, ftp accounts, etc) of the master domain. Secondary domains have their own stats, bandwidth recording, and web space. They are essentially another domain/website under the same SiteWorx account. They can also be used to create subdomains with their own segregated storage and bandwidth statistics.
The number of subdomains allowed for SiteWorx accounts created using this package. A subdomain allows you to add a sub.domain.com to your account which feeds from the domain.com/sub subdirectory in the main html document root. Can be useful in creating the illusion of multiple sub-sites if Secondary Domains are restricted.
Determines if a SiteWorx account can recreate backups of their account in SiteWorx. For very large accounts, creating backups can be resource intensive, which is why this option is made available. If this is set to No the SiteWorx user will not be able to create account backups from SiteWorx and the NodeWorx user will have to create them for them.
Determines if a SiteWorx account has CGI script access. If this is set to No SiteWorx accounts created using this package will be unable to run CGI scripts.
Determines if a SiteWorx account has access to the CRON tab and can setup/modify CRON jobs.
Determines whether or not to resolve an ip address to a domain name for stats purposes. If this option is set to Yes, your statistics will reflect a human readable domain name rather than the ip address of the site. Reverse resolution of IP address can take an extended amount of time and can slow stats generation considerably.
Enables SSL certificates for a SiteWorx account.
Determines what happens when a SiteWorx account reaches its bandwidth quota. If this option is set to Yes, the SiteWorx account will be able to go over its bandwidth allotment, perhaps at an extra cost (depending on the bandwidth agreement). If this option is set to No, the SiteWorx account bandwidth will be capped at a predefined limit and transfer of data will be stopped once the transfer limit is reached. Stopping data transfer is equivalent to having the site "turned off".
Determines if transfer logs will be available for download and offline analysis. If this option is set to Yes, web transfer logs will be saved in a format that can be downloaded and analyzed offline. If this option is No, the web transfer logs are not saved and cannot be downloaded.
Note: Deleting a SiteWorx account will delete all of the files and data associated with that account.
If the day that you choose for the billing day is after the current billing day, the billing period will end on the day before the billing day at 11:59 p.m. and the new billing period will start at 12:00 a.m. on the billing day. The start of the billing period is not changed, therefore changing the billing day to a day later than the current one will result in an elongated billing period.
If the day that you choose for the billing day is before the current billing day, the billing period will end on the day before the billing day at 11:59 p.m. and the new billing period will start at 12:00 a.m. on the billing day. The start of the billing period is not changed, therefore changing the billing day to an earlier day than the current one will result in a shortened billing period.