Profile Workflows
The profile is the site type. It changes which files are created, whether PHP/DB/cron are needed, and which application actions appear under Applications.
Use this guide when the menu asks for a profile during:
Sites -> Create site
Quick Rule
| Profile | Use For | Continue In |
|---|---|---|
generic |
Simple PHP site without CMS-specific automation. | Generic PHP |
static |
Static HTML/files, no PHP, no DB, no cron. | Static |
alias |
Extra domain pointing to an existing site. | Alias |
laravel |
Laravel project with Composer, .env, scheduler, and queue worker. |
Laravel |
wordpress |
WordPress site with WP-CLI, installer readiness, cron, and cache actions. | WordPress |
bitrix |
1C-Bitrix site with Bitrix nginx routing, PHP baseline, cron agents, cache, restore, and ownership checks. | Bitrix |
What Site Creation Does
Sites -> Create site creates the infrastructure layer:
- project directory under
/home/simai/www/<domain> - nginx config
- PHP-FPM pool when the profile needs PHP
- healthcheck
- optional SSL
- optional managed DB/user
- managed cron file when the profile supports cron
It does not always complete the application itself. For Laravel, WordPress, and Bitrix there is a second step after the application is real or after the browser installer has finished.
Common Menu Route
After creating any site:
Sites -> Site info
Diagnostics -> Site health check
For CMS/framework sites, also open the matching submenu:
Applications -> Laravel
Applications -> WordPress
Applications -> Bitrix