Projects Overview
The Projects page keeps a compact list beside the selected project's details. Projects normally live under C:\laraenv\www\<name> and use a local domain such as <name>.test. The configured projects root can be changed in Settings; portable installations use their own root.
LaraEnv watches the projects folder and generates the virtual hosts and Windows hosts-file entries needed to serve detected projects. The list shows the name, path, stack, PHP and Node resolution, and tags.
Find a project
Use Client tags as the main filter for customers, teams, or other labels you choose. The selector shows project counts, lets you search tags, and includes All tags and Untagged. Click a tag in a row to filter by it. Add or edit tags from the project's details panel.
The visible search matches project names, paths, and tags. Combine it with a client tag to narrow the list. Clear filters returns to all projects.
Projects are sorted by name and shown in pages of 10 by default. Choose 20 or 50 under Projects per page. The footer shows the visible range and total. Changing a filter or page size adjusts the current page.
Customize row actions
Open Customize actions to choose the two shortcuts displayed on every row: Editor, Browser, Terminal, or Folder. Choose Hidden to leave either slot empty. Selecting an action already used by the other slot swaps their positions; Restore defaults returns to editor and browser.
This preference is saved on this device. Editor and terminal shortcuts use your existing project and global preferences, including custom commands. They launch the action without changing the selected project. See Project configuration.
Project details
Select a row to open its details. The panel contains quick launch controls, development and Laravel queue controls, project scripts, a custom-command field, PHP and Node selectors, project tools, and copy buttons for the domain and path. Tools include Site Doctor, HTTPS, virtual-host configuration, history, cron, tags, and deletion.
Development is available for projects with package.json even when LaraEnv does not recognize a framework. Project scripts lists the scripts actually defined in that file, such as dev, watch, or build; use Refresh scripts after editing it. Scripts and custom commands open in a project terminal using its runtime and terminal preferences. Laravel projects also show a dedicated Queue worker control. See Development, scripts, and queues.
On wide windows the panel appears beside the list. On smaller windows it opens over the list; close it with its close button or Escape. If the selected project leaves the current page or filtered results, its details close.
The list, panel, selection, and buttons follow the theme chosen in Settings → Appearance.
Shared services and project processes
Web server running/stopped describes the shared web server. PHP pools are shared per PHP version and can serve several projects. Projects do not have separate start/stop instances for these services.
Start Dev / Stop Dev and Start queue / Stop queue control background processes belonging to the selected project. These controls do not prove that every application route or database connection works. Run Site Doctor to inspect the project's setup.
Running a script or custom command opens a terminal instead of creating another managed Dev process. Use that terminal to follow output and stop a long-running command with Ctrl+C.
Local domains
The global TLD selector changes the domain suffix for all projects, for example .test, .local, or .dev, and regenerates their web configuration. .test is the default reserved testing suffix.