Project Configuration
Select a project in the Projects list to open its details panel. Project settings are persisted in config.json under projects.
PHP and Node
Choose Automatic to resolve the runtime from the project's declarations, or choose an installed version to keep a manual override. The panel shows the effective version, its origin, and the requirement it is satisfying. A missing or incompatible version includes guidance and a Downloads shortcut when available.
PHP pools are shared by version. Choosing PHP for a project changes its web-server upstream and the PHP used by new project commands. Node controls the tooling and dev server. Existing shells and background processes keep their runtime until restarted. See Automatic detection, PHP, and Node.js.
HTTPS
The SSL control generates a certificate signed by LaraEnv's local certificate authority and updates the virtual host for HTTPS. Installed editions attempt to trust that authority automatically. Portable editions ask before trusting it in Windows; you can also review its identity and trust status in Settings.
If the browser reports a certificate problem, check the CA trust status rather than treating every warning as expected. See Virtual hosts and Troubleshooting.
Quick launch
The editor and terminal menus choose the tools used for this project. They support installed applications and the existing custom-command preferences. A global default is used when no project preference is set.
The row's customizable actions use these same preferences. The choice of which two actions appear in the list is stored separately on this device.
Tags
Use free-form tags for clients, teams, or other categories. Edit tags in the details panel and filter by them in the main list.
Development, scripts, and queue
Start Dev runs the saved development command or uses the package manager detected for the project to run its dev script, falling back to start. This control is available for projects with package.json even without a recognized framework. Choose Configure command while the process is stopped to save a different command; a project command takes precedence over the global default. Use {port} in a custom Dev command when it needs LaraEnv's chosen port.
Project scripts reads script names from package.json. Choose a script to see the command before running it, or enter a command in Custom command. These commands use the project's terminal preference, working directory, and resolved PHP and Node runtimes. Running one does not change your terminal preference or replace the saved Dev command. Scripts such as build and watch run as written, without Dev-server port flags.
The Laravel Queue worker controls include start, stop, restart, and saved arguments. They remain available for Laravel projects without a JavaScript framework or package.json.
A proxy port forwards the project's local domain to localhost:<port>, which is useful for Node framework servers. See Development, scripts, and queues.
Project tools
The panel also includes Site Doctor, virtual-host configuration, history, cron, and deletion. Creating projects and changing the global domain suffix remain in the page header.