Hosting Packages

Last updated

/jabali-admin/packages. A Package is a bundle of quotas and limits assigned to a user.

Fields

FieldUnitPurpose
Name, slug, description—Identifier and display label
disk_quota_mbMiBPOSIX disk quota applied to /home/<user>
bandwidth_quota_mbMiB / monthMonthly web traffic the user’s domains sent to visitors, search engines and other bots included. The admin is notified at 80% and 100%; the websites are suspended only when Bandwidth Quota Auto-Suspend is on (see Resource limits). 0 = unlimited
memory_limit_mbMiBMemoryMax= on the user’s systemd slice
cpu_quota_percent%CPUQuota= on the user’s systemd slice
io_read_mbps, io_write_mbpsMB/sIOReadBandwidthMax= / IOWriteBandwidthMax= on the user’s systemd slice
max_tasksintTasksMax= on the user’s systemd slice
max_domains, max_email_accounts, max_databases, max_database_usersintHard caps enforced at create time
php_settings_policyobjectWho may change each directive on a domain’s PHP Settings page for users on this package: memory_limit, upload_max_filesize, post_max_size, max_input_vars, max_execution_time, max_input_time, display_errors, error_reporting, date.timezone, log_errors, file_uploads, short_open_tag. Each is Tenant can change (tenant_allowed, the default, which is what tenants could already do) or Admin only (admin_only). An admin-only directive shows read-only to the tenant with Set by your administrator; its value still applies, and a tenant API request that changes it is refused (403 php_setting_not_permitted). Admins can always set every directive, including while impersonating the tenant. An account with no package gets the defaults. The security-sensitive directives open_basedir and allow_url_fopen are Admin only by default; Tenant can change (checked) (tenant_privileged) is the explicit opt-in, and the server still checks every value: a tenant may only narrow open_basedir to folders inside their own home. The other security-sensitive directives (disable_functions, mail.force_extra_parameters, include_path, session.save_path) accept the same two levels but are not per-domain settings, so their level changes nothing. Stored as a JSON object of directive to level (empty = defaults). Editor: PHP settings tenants may change; CLI: --php-settings-policy '{"memory_limit":"admin_only"}'.
webmail_enabledboolWhether tenants on this plan get webmail (the Bulwark UI). Defaults ON, including the auto-assigned default package. Webmail is governed by this package flag AND the per-domain domains.webmail_enabled flag. For any tenant whose package has webmail off, mail.<domain> no longer serves the webmail app and the webmail SSO login gate refuses redemption. Mail apps keep what they use there: autoconfig/autodiscover, CalDAV/CardDAV and JMAP, as with IMAP and SMTP. An account with no package keeps webmail on (a deliberate exception — webmail is a convenience surface, not a hardening clamp). The former per-user toggle (users.webmail_enabled) was removed; a backfill migration copied each user’s OFF intent down to their domain rows, so nothing changed for existing tenants. Migration 000312 dropped the column itself. Flipping this flag in the panel kicks an immediate reconcile; a CLI --webmail edit converges on the next periodic sweep instead (the sweep is the safety net either way). Set it per package via the editor or --webmail=false on the CLI.
composer_enabledboolWhether users on this plan may run Composer for their domains from the panel: install, update, require, remove, audit and other commands, as their own user, on the domain’s PHP, in their SSH sandbox. A run executes the project’s composer.json scripts with PHP Defense’s command-execution bans lifted, so it amounts to running commands in that sandbox: grant it as you would SSH access. Off for every package, existing ones included; an account with no package can’t run Composer (a privileged feature). In the package editor it is the Composer switch under Features; on the CLI, --composer.
git_deploy_enabledboolWhether users on this plan may deploy their domains from a Git repository: connect a repository (an https URL, a branch, and a token for a private repository), deploy it by hand or on every push through a webhook, and roll back to an earlier release, from the domain’s Git tab. A deployment runs the user’s own deploy commands (php, wp) in their SSH sandbox, so grant it as you would SSH access. A project with composer.lock and no vendor/ also needs composer_enabled. Off for every package, existing ones included; an account with no package can’t use it (a privileged feature). In the package editor it is the Git deploy switch under Features; on the CLI, --git-deploy.
website_sends_emailboolWhether the sites of users on this plan may send email with PHP mail() (contact forms, WordPress). Applies whichever way website mail goes (Server Settings → Email → Website mail): through the local mail server, a site without it loses its relay identity (its credential file is removed and the relay password rotated); through a smarthost, its user is left off the relay’s sender list. Migration 000317 turned it on for every package that existed then, and the seeded starter plans and Plesk imports have it on; a package created in the panel or CLI starts with it off. An account with no package can still send through the local mail server, but never through a smarthost (the smarthost sends with the operator’s login and reputation). Set it with the editor’s “Websites can send email” switch or --website-mail on the CLI.
redis_keys_per_callintHow many keys one call of the Redis key browser API may list (its limit) or delete for users on this plan, 100 to 5000. Default 500, which is what every plan had before it was a setting (migration 000326). Unlike the other limits, 0 does not mean unlimited: it is refused. Each call still scans for at most 5 seconds and is rate-limited per user, so a higher value means bigger pages, not more work per call. Users with no package get 500. Set it with the editor’s “Redis Keys per Call” field or --redis-keys-per-call on the CLI.
php_disabled_functionslistThe PHP functions this package’s sites cannot call: the disable_functions list of their PHP pools. Empty (null) is the default, which disables every command-execution function: exec, passthru, shell_exec, system, proc_open, popen, pcntl_exec, pcntl_fork, proc_nice, dl. Uncheck one of them in the editor (Disabled PHP functions) to let the sites call it, and add any other function under Also disable. Allowing a function is a security risk: only do it for plans whose apps need to run commands. Allowing system, exec, shell_exec, passthru, popen, proc_open or pcntl_exec also lifts PHP Defense’s ban on that function for these sites, so it works in enforce mode too. What an allowed function can then start depends on the jabali-fpm-app AppArmor profile: in enforce mode only the shell and cat; in complain mode (it only logs) or when the profile is not loaded, any program the site’s user can run, which for anyone who takes over such a site is the same as shell access. The editor says which applies on this server as soon as one of those functions is allowed. A change reaches the sites within seconds. Tenants cannot change the list; they see the result read-only on a domain’s PHP Settings page. php_exec_enabled (the old Allow PHP exec functions switch) is now derived: it reads true when none of the ten is disabled. Setting it to true allows all ten and false disables all ten; other functions on the list stay. When both are sent, the list wins. CLI: --php-disabled-functions "exec,passthru,mail", or default, or none.
egress_ssh_outboolLets users on this package open outbound SSH connections (TCP port 22) from their shell, for example git over SSH. Default off. It changes nothing for a user whose outbound firewall is not enforced or learning. An account with no package never gets it. Set it in the package editor (Allow outbound SSH (port 22)) or with --egress-ssh-out on the CLI.
egress_ssh_out_cidrslist of CIDRsWhere outbound SSH may go, e.g. 203.0.113.0/24 or 2001:db8::/32. Empty means any destination. Stored as a JSON array; the API rejects anything that is not a valid CIDR. The cloud-metadata ranges (169.254.0.0/16, fe80::/10) stay blocked even for 0.0.0.0/0. Shown in the editor as Outbound SSH destinations when outbound SSH is on; --egress-ssh-out-cidrs on the CLI.
egress_icmpboolLets users on this package send ping (ICMP/ICMPv6 echo requests only) from their shell. Default off; same enforced/learning and no-package rules as egress_ssh_out. Editor: Allow ping (ICMP echo); CLI: --egress-icmp.

List page

Each row shows the package name, the number of users assigned, total quota allocated, and total disk in use across those users.

Actions: Edit, Delete, Duplicate.

Lifecycle

  • Create: see Create Package.
  • Edit: see Edit Package. Changes converge to every assigned user on the next reconciler tick (within 60 seconds).
  • Delete: forbidden if any user is assigned. Reassign users first.

Default package

The installer creates a default package suitable for small VPS scale (10 GiB disk, 1 GiB RAM cap, 50% CPU, 5 domains, 25 mailboxes, 5 databases). Edit it freely; the row identity is the slug default, so do not rename it if you rely on the auto-assignment to “default” when creating users without an explicit package.

CLI

jabali package list
jabali package create --name standard --disk-mb 5120 --memory-mb 512 --cpu 25 …
jabali package edit <package-id> --memory-mb 1024
jabali package delete <package-id>