Applications, domains and files

Create a custom PHP application

Where to find: Applications → Create an Application → Custom

Use Custom to prepare the environment of a project whose files will be sent by you. Check out the runtime and public directory required by the project.

1. Click Create an Application and fill in Application Name.
2. Choose Primary Domain for your domain or Test Domain for a test address.
3. For your own domain, fill in the address without protocol or path. Check out the options Also add www version of the Domain and Secure your application with SSL certificate.
4. In Select a Method, choose Custom.
5. Review Install Log Monitoring Suite. The form warns that this option can increase CPU and memory.
6. Open Show Advance Options. In System User, choose Create New or Choose From Existing and check out the user responsible for the files.
7. Select PHP Version and Custom Webroot when your project requires a different public folder. The field quotes public as Laravel's example; use your project path.
8. Click Create Application, wait and confirm the application in the list.
9. Post the files through File Manager or SFTP, set up the database and test the domain.

Use the One Click installer

Where to find: Applications → Create an Application → One Click

The catalog changes with server technology. In the OpenLiteSpeed review, One Click presented WordPress and phpMyAdmin. The other items below come from the site catalog; confirm your presence in the corresponding stack.

1. Fill out name and type of domain in the creation form.
2. Choose One Click and select a listed application.
3. Complete the specific fields displayed for the application. Do not use administrator data from one software as credentials from another.
4. Check out advanced banking, system user, runtime and webroot options.
5. Review SSL, monitoring and application-specific options.
6. Click Create Application, wait for the result and open the domain.
7. Complete the configuration within the installed software and test login, data recording and uploads.
8. Prepare a first copy and backup routine before putting the project into use.

Install WordPress with Panel Fields

Where to find: Create an Application → One Click → Wordpress

The WordPress form distinguishes administrative credentials, database data and system user. Prepare your domain and a valid administrative email.

1. Select Wordpress in One Click.
2. In Admin Information, fill in Username, Email and Password from the WordPress administrator.
3. If you want a standardized configuration, select an existing Blueprint. Add Blueprint opens the creation of a new pattern.
4. Check out Enable Search Indexing: Use the appropriate configuration for the production or testing site.
5. In OpenLiteSpeed, review Install LiteSpeed Cache Plugin as per your cache strategy.
6. In Show Advance Options, check out Site Title, Site Language and Timezone.
7. Check out Database Name and Database Prefix; this data is not the SSH user.
8. Choose the system user and compatible PHP version. Review domain, SSL and webroot.
9. Click Create Application, wait and test the site and administration. Check WP Toolkit for the preferences, plugins and themes applied.

Procedures for other applications

Where to find: One Click → compatible application; initial configuration within the software

Use the common installer procedure and then complete the tasks specific to each application. Individual Apache, Nginx PHP and Node.js stack forms were not accessible on the revised OpenLiteSpeed server.

Understand the fields and options

PrestaShop

Check domain, administrator and database in the installer. Then set up catalog, currency, means of payment, shipping and store messages within PrestaShop; test a purchase in a test environment.

Moodle

Check runtime, database, data directory and cron routine required by the version. Inside Moodle, complete administration, users and courses; test access and execution of tasks.

Joomla

Check domain, database, and administrator; then adjust content, menus, users, and extensions in Joomla and test public pages.

Mautic

Check database and cron commands required by the version. Set up email, domain authentication, contacts and campaigns on Mautic; validate a test journey before firing campaigns.

Akaunting

Check installation and database; complete organization preferences and users in the application and test financial records with test data.

Nextcloud

Plan storage, database, and background tasks. Configure users and permissions in Nextcloud and test upload, download, and share; include files and database in recovery.

Craft CMS

Check PHP, extensions, database, and public folder required by the project. Complete CMS administration, content, and configuration after deploy.

Statamic

Check project requirements, webroot, permissions and persistence form. Publish the files and configure users and content in the application.

phpMyAdmin

One Click offers the tool in OpenLiteSpeed. Do not confuse creating the phpMyAdmin application with creating a database or granting access to all databases; use appropriate SQL credentials.

n8n

Check runtime, persistence and database supported by version. Set up credentials and workflows within n8n, test with test data, and preserve the settings required for recovery.

Uptime Kuma

Configure monitors and notification channels in the software; test a controlled failure and consider that the server's own failure can stop monitoring.

Node-RED

Configure editor, authentication, streams, and integrations in the application. Test the flow deploy and include persistent data in the recovery routine.

NodeBB

Complete database, administrator and forum configuration; login test, posts and uploads. Check project dependencies and persistence.

Publish Node.js applications

Where to find: Server with stack Node.js → Applications

The Node.js stack is displayed in beta in the site catalog. Your forms and execution controls need to be used according to the Node.js environment, without copying PHP fields.

1. Open a server with the appropriate stack and check out the runtime version.
2. When creating, choose the listed application or publication method for your project.
3. Configure domain and execution parameters effectively offered: command, internal port, variables and build when requested.
4. Check the database and persistence volumes/directories required by the software.
5. Complete the publication and testing of domain access and flows that record data.
6. Check process, logs and restart, and prepare a recovery of persistent files, database, and settings.

Post an application by Git

Where to find: Create an Application → Git; Integration → Git

Connect the provider before choosing the account and repository in the creation. Check out branch and webroot before deploying.

1. Vincule Github, Gitlab or Bitbucket in Integration → Git.
2. Fill in name and domain and select Git.
3. Choose the provider and complete the displayed repository and branch selectors.
4. Check system user, runtime and Custom Webroot in advanced options.
5. Complete deployment, see the logs and test the domain.

Add domain and set the main

Where to find: Application → Dashboard → Application Domains

The domain list is on the Dashboard of the application. Signing up to the panel and configuring DNS to the provider are separate tasks.

1. Open Dashboard and locate Application Domains.
2. Use Add to Domain and inform the domain requested by the form.
3. Confirm the item in the list and select the main domain by primary domain column control when needed.
4. In the DNS provider, adjust domain registration to the server address; preserve email records and other services.
5. Confirm the resolution before updating the SSL certificate.
6. Test main domain and aliases. The removal in the panel does not automatically remove records in the DNS provider.

Check certificates and redirect to HTTPS

Where to find: Application → SSL Certificate

After adding a domain, wait for DNS to point to the correct destination before issuing or updating the certificate.

1. Open SSL Certificate and see the status.
2. If there is no certificate, use the installation method offered and check the domains included before starting.
3. Wait for the result and check out Issued on, Valid until and the domains covered.
4. When HTTPS is working, review Force HTTP to HTTPS to redirect traffic.
5. Test main domain, aliases and pages with images and scripts.
6. After adding domain, review SSL coverage. Do not remove valid certificate only to resolve mixed content.

If the result is not expected

Send and manage files

Where to find: Application → File Manager

The manager presents path, search, hidden files and actions by selection. Check the directory before any operation.

1. Open File Manager and use breadcrumb to confirm application and folder.
2. Use Copy Path to check the path; the observed default webroot is public_html.
3. Use Upload for upload, New File for a file and New Folder for a folder.
4. Select the item before using Copy, Move, Rename, Download, Compress or Change Permission. Actions may be disabled without a proper selection.
5. In search, choose Current Directory or Recursive Directory as per scope.
6. Activate Show hidden files when you need hidden project files.
7. Before editing, replacing or Delete, keep a copy. Once finished, test the application.

If the result is not expected

Associate the application to the correct database

Where to find it: Application → Dashboard → Database Details

Check out Database Name, Remote Access and user shortcuts and phpMyAdmin. SQL credentials may differ from the user responsible for the files.

1. Identify the database on the Dashboard.
2. Open your name to refer to Database Users.
3. Configure the application with the correct host, name, user, and password.
4. Test read and write. Before removing an association or database, check the dependencies.

Manage users and access to the database

Where to find: Databases → database → Database Users

Each connection must use the appropriate credential and origin.

1. Open the database and create or edit the required user.
2. Check out Connection Preferences.
3. Update the application credentials and test the connection.

PHP adjustment per application

Where to find: Application → PHP Settings

The fields control version, session, access to PHP directories and limits. They do not extend the physical resources of the server.

1. Check the required PHP version and install it in Services if not listed.
2. Open PHP Settings and choose PHP Version and Timezone.
3. Review Session GC Maxlifetime, Auto Prepend File and Open Basedir only as required by the project.
4. Adjust Upload Max Filesize, Post Max Size, Memory Limit, Max Execution Time, Max Input Time and Max Input Vars.
5. For uploads, consider the file and the total size of the request; Post Max Size needs to contain the submitted data.
6. Preserve Disabled Functions unless technical need is verified. Extra PHP Configuration requires checking the effect of the directive.
7. Click Update Settings and test the changed function.

Create staging and a copy of the site

Where to find: Application → Staging Area / Site Clone

Staging Area appears as beta. It is a test environment; do not assume that the test domain is password protected without setting up and checking access.

1. In Staging Area, fill in Staging Area Name.
2. Choose Primary Domain or Test Domain, enter the address and select Database.
3. In WordPress, check out Force URL: Http or Https. HTTPS requires appropriate certificate and configuration.
4. Click Create Staging Area, wait and test the copy.
5. In the synchronisation options available after creation, check the direction: production for staging replaces copy; staging for production can replace recent production data.
6. For an independent copy, open Site Clone and choose Application, File System or Database.
7. Check out New Application Name, Source Database, New Database Name, domain and system user. For WordPress, check out Force URL.
8. Click Clone and follow Clone Summary Site. Review emails, payments, cronjobs and integrations to prevent duplicate actions in the copy.

Open WordPress Tools

Where to find: Application → WP Toolkit

Toolkit concentrates maintenance, versions, plugins, themes, cache, cron, security and WordPress preferences.

1. Open the WordPress app and select WP Toolkit.
2. See Overview for versions and components.
3. Open the specific guide before using tools that change bench, components or tasks.

Use a WordPress installation pattern

Where to find: WP Blueprint; WordPress creation → Blueprint

Blueprint saves plugins, themes and preferences for new installations. It is not a backup of the content of an existing site.

1. Create and review the pattern in WP Blueprint.
2. In the new WordPress installation, select this pattern in the Blueprint field.
3. Check out on the website created the components, indexing, debug and applied preferences.

Protect and configure the application

Where to find: Application → Security / AI Bot Blocker / Fail2ban / Settings

Project protections and settings are different from the server port firewall.

1. In Security, check out the 8G Firewall control, displayed as beta; login test, forms and APIs after changes.
2. In AI Bot Blocker, check out the blocking of known crawlers. This can change how automated services access your content.
3. In Fail2ban, review project specific jail and filter according to the safety guide.
4. In Settings, check out Change Custom Webroot before Update. An incorrect path can take the site off the air.
5. Fix Permission fixes property/permissions; use after identifying the error and check files with special requirements.
6. Basic Authentication adds user and password to site access; it is useful for a test environment, but it can block webhooks.
7. Maintenance Mode shows a message during maintenance; disable and test the site upon completion.
8. Delete Application permanently removes application and associated data. Back up and check the destination before confirming.