Lizenzportal
English

HostingSubscriptionAdd

With this function, a new web hosting subscription can be created.

If the new web hosting subscription is created within a reseller subscription, the name of the respective reseller subscription must be specified in resalecontract. If resalecontract is left empty, the fields webserver, mailserver and dbserver must be used to specify the names of the servers on which the respective services (webspace, email, databases) shall be deployed.

If the field plan is left blank, an individual hosting package will be set up. Otherwise, the specified hosting plan is used as a basis and differing parameters (webspace, databases, etc.) are managed as „special settings“.

The subscription name (subscriptionname) must be unique across the system.

If the password starts with $1$, LiveConfig assumes that it is already an MD5 password hash and not a plain text password. This is then written unchanged as a password in /etc/shadow. However, this does not work on systems with SELinux activated!

If the field customerid is left blank, LiveConfig creates this hosting subscription under „My hosting“.

Request

Field

Type

RegExp

Null?

Description

auth

AuthData

no

Authentication data

subscriptionname

string

^[a-z][a-z0-9_-]{0,31}$

no

unique subscription name

password

string

^.{5,63}$

yes

Password for the subscription account (e.g. FTP password)

resalecontract

string

^[a-z][a-z0-9_-]{0,63}$

yes

Name of the reseller subscription under which this subscription is to be created

webserver

string

^[\w.-]{1,255}$

yes

Name of the web server on which the webspace is to be set up

mailserver

string

^[\w.-]{1,255}$

yes

Name of the mail server on which the mailboxes are to be set up

dbserver

string

^[\w.-]{1,255}$

yes

Name of the database server for this subscription

customerid

string

^[\w.-]{12}$

yes

ID of the customer to whom the contract is to be assigned (NULL: „My Hosting“)

plan

string

^.{1,50}$

yes

Name of the hosting plan

maxcustomers

integer

^-?\d{1,8}$

yes

Maximum number of customers for resellers (NULL: no reseller subscription, -1: unlimited)

maxusers

integer

^-?\d{1,8}$

yes

Possibly different number of users (-1: unlimited)

webspace

integer

^-?\d{1,8}$

yes

Possibly different webspace size (MB) (-1: unlimited)

ssi

integer

^[01]$

yes

Possibly different SSI setting (Server-Side Includes)

php

integer

^[0123]$

yes

Possibly different PHP mode (0: no PHP, 1: suPHP, 2: FastCGI, 3: mod_php, 4: FPM)

cgi

integer

^[012]$

yes

Possibly different CGI setting

ssl

integer

^[012]$

yes

Possibly different SSL setting (HTTPS) (0: no, 1: yes, 2 yes (with certificate management)

cronjobs

integer

^-?\d{1,8}$

yes

Possibly different number of cron jobs (-1: unlimited)

apps

integer

^-?\d{1,8}$

yes

Possibly different number of installable web apps (-1: unlimited)

ftpaccounts

integer

^-?\d{1,8}$

yes

Possibly different number of FTP accounts (-1: unlimited)

shellaccess

integer

^[012]$

yes

Possibly different shell access (0: no, 1: scponly/sftp, 2: yes (bash))

databases

integer

^-?\d{1,8}$

yes

Possibly different number of databases (-1: unlimited)

subdomains

integer

^-?\d{1,8}$

yes

Possibly different number of subdomains (-1: unlimited)

extdomains

integer

^-?\d{1,8}$

yes

Possibly different number of external domains (-1: unlimited)

mailboxes

integer

^-?\d{1,8}$

yes

Possibly different number of mailboxes (-1: unlimited)

mailaddrs

integer

^-?\d{1,8}$

yes

Possibly different number of e-mail addresses (-1: unlimited)

mailquota

integer

^-?\d{1,8}$

yes

Possibly different mail storage size (-1: unlimited)

traffic

integer

^-?\d{1,8}$

yes

Possibly different IP traffic limit (-1: unlimited)

webstats

integer

^[012]$

yes

Possibly different web statistics setting (0: no stats, 1: Webalizer, 2: AWStats)

logfilter4

integer

^[0-4]$

yes

Possibly different IPv4 address filtering in access.log (number of bytes to be filtered; 0-4)

logfilter6

integer

^[0-9]|(1[0-6])$

yes

Possibly different IPv6 address filtering in access.log (number of bytes to be filtered; 0-16)

comment

string

^.{1,100}$

yes

Optional comment
Response

Field

Type

Null?

Description

id

string

no

Data record ID

subscriptionname

string

no

Subscription name
Zuletzt aktualisiert am 29.06.2020.
weiter: HostingSubscriptionDelete
zurück: HostingSubdomainEdit