Creating a host packages with package


In the control panel which use hosting server, they must have function creating host packages, and these packages will be assigned when creating the user (User). For example, in each host package we can prescribe the number of domains that users are allowed to add to, the number of the database, the number of emails, hard drive capacity and of course the bandwidth capacity can be used.

In VestaCP, this host package section is also called Package and I will talk in detail about settings relating to Package in this article.

The default host packages

When installing VestaCP, they default gave us 4 different host packages, and default packages for admin account is default. You can see the list of available host packages in the Packages menu in admin page.

The list of the default package in VestaCP:

These packages will provide the setting for users who use the package.

You should delete these packages which you do not use and create their own hosting packages to manage easier.

How to create a new host packages

In th packages section on the menu, you click the green plus button to start creating a new hosting package.

When creating the package, we will have the following settings:

The needed information when creating a host packages in VestaCP

You should look through an explanation of the parameters; I would say how you should set the parameters later.

  • Package Name: The name of the host package.
  • Web Template: Template sets up Apache. Note that if you choose NGINX + PHP-FPM when creating installation command, it will be the other template. I will say about this part in another post.
    • default: Does not contain the option settings..
    • basedir: Use to anti shell on the website by PHP executable limiting folders with open_basedir. Only use when necessary.
    • hosting: Limit resources to execute PHP on each domain, such as limit memory and storage which is allowed to upload, …
    • phpcgi: Run PHP inApache by  CGI instead of Apache with mod_php as usually.
    • phpfcgid: Run PHP in Apache by FastCGI.
  • Proxy Template: Template contains NGINX settings doing Reverse Proxy for Apache..
    • default: NGINX saves cache for static datas.
    • hosting: Prevents accessing the symbolic link.
    • caching: NGINX will save cache of the entire page on the website each 15 minutes. Only use when the site is overloaded.
    • php-fpm: Allow NGINX to do backend and run PHP with PHP-FPM.
  • DNS: The DNS setting templates of user.
    • default: Normal DNS setting.
    • gmail: Setting contains the records to use Google App Business. However, we should not choose it because we can add records to the following Google Applater.
    • child-ns: Record setting uses Vanity nameservers. It means symbolically DNS address.
  • SSH Access: Setting allows accessing into the server by SSH protocol.
    • sh: Use/bin/sh
    • bash: Use /bin/bash
    • nologin: Use /sbin/nologin. It means not allow using SSH.
  • Web Domains: The number of domain is allowed to use.
  • Web Aliases: The number of nicknames domain is allowed to use on each domain in the package, also known as an alternative domain for the main domain.
  • DNS Domains: The number of settings packages which DNS is allowed to use.
  • DNS Records: The number of records allow to enter each package DNS.
  • Mail Domains: The number of e-mail which is used as e-mail domain as is allowed to use.
  • Mail Accounts: The number of email accounts is allowed to use on each mail domain.
  • Databases: The number of databases is allowed creating.
  • Cron Jobs: The number of databases is allowed creating.
  • Backups: The number of stored copies is allowed on the system. This backups are backups for users, all users will be backed up daily.
  • Quota: Storage capacity is allowed using (measured by MB).
  • Bandwith: Bandwith is allowed using (measured by MB).
  • Nameservers: Fill your two DNS addresses created in the previous post here. This is the DNS address settings for users to use this package.