ScriptExpert Local Development Stack Explained

ScriptExpert Code Editor ships with a built-in local development stack, so you can go from a freshly installed desktop to a running PHP application without juggling separate installers, configuration files and background services. The stack is installed and managed from inside the editor, and every project can choose the runtime it needs.

What’s included

The local development stack bundles the tools most PHP web projects depend on:

• PHP — a supported runtime with a working php.ini and the extensions common frameworks expect, including OpenSSL.
• Composer — dependency management for Laravel and other PHP projects.
• Apache — a local HTTP server for classic PHP files and framework public entry points.
• MariaDB / MySQL — a local database engine for your application data.
• Node.js — JavaScript tooling for front-end asset builds and npm-based workflows.

How the tools are installed

ScriptExpert installs these tools as extensions, and delivery depends on your platform.

Windows

On Windows each tool is a portable package stored under your user’s ScriptExpert data directory — no system-wide service registration needed. Packages are downloaded from the configured extension catalog and verified against a published SHA-256 checksum before installation. PHP and Apache include the required Visual C++ runtime DLLs so they also start on a clean Windows installation.

Linux

On Linux ScriptExpert uses your distribution’s package manager, because PHP and Apache do not publish one binary that works everywhere. After verifying a small signed catalog recipe, the editor asks for authorization through polkit/pkexec and installs the runtimes with apt-get, dnf, pacman or zypper. The distribution itself downloads, verifies and updates the runtimes.

Choose a PHP version per project

Different projects often need different PHP versions. ScriptExpert lets you select the installed PHP version for each project individually, so a legacy project and a current Laravel application can coexist on the same machine without global version switching.

Apache, virtual hosts and the document root

Classic PHP files and framework public entry points (like Laravel’s public/index.php) can be served through the configured Apache address and port. The editor understands the application’s public directory, so Preview opens the correct entry point instead of the project root.

MariaDB / MySQL

The local database engine keeps your data under the ScriptExpert data directory. MariaDB data is preserved during runtime updates, so updating the editor does not wipe your local databases.

Node.js for front-end builds

Node.js is available for projects that compile assets, run build scripts or use npm-based tooling, keeping the PHP backend and JavaScript front end in one workspace.

Preview and routes

ScriptExpert detects the project framework and uses it to drive Preview:

• An already running Laravel preview server is reused instead of starting a new php artisan serve process every time.
• Laravel startup output is shown in the Preview window while the server is preparing.
• Preview respects the project framework, the configured URL and the project port.
• Supported frameworks can expose their routes to the editor, so Preview follows the correct application entry point.

Project dashboard and health checks

The project dashboard surfaces stack information, running services, source statistics, integrations and health checks. If a runtime is missing or misconfigured, the editor can guide you to install or repair it — for example, repairing the PHP configuration when a required extension such as OpenSSL is not enabled.

Windows and Linux

ScriptExpert follows the same product workflow across supported Windows and Linux releases. Editions and release channels are kept separate so each installation receives a compatible build for its platform and architecture.

Getting started

1. Open your PHP project in ScriptExpert.
2. Install the extensions you need from the extension catalog: PHP, Composer, Apache, MariaDB/MySQL and Node.js.
3. Select the PHP version for the project.
4. Start the services and open Preview — ScriptExpert follows the framework’s public entry point.

From there, editing, terminal commands, database work and Preview all happen in the same workspace, with the local development stack managed for you.

Explore ScriptExpert Code Editor and set up your local development stack today.