Laravel application

Coduva installs a new Laravel project with Composer, connects the .env file to MariaDB and runs the first migration. Day-to-day tasks (Artisan commands, queue, scheduler, Vite) are done from the project screen.

New Laravel project

1. Click Projects → New project (or Ctrl+K → Create new project).
2. Select Laravel as the template.
3. Enter a Project name, e.g. panel. The address becomes panel.test.
4. The Location line shows the project folder (C:\Coduva\www\panel). To use a different parent folder, click Change.
5. Optionally, choose a PHP version and check the Use HTTPS box.
6. Click Create.

Internet required

Laravel packages are downloaded from the internet with Composer. Depending on your connection speed, setup can take several minutes. Progress is shown live.

Setup consists of the following steps:

1. The composer create-project laravel/laravel panel command runs.
2. A database dedicated to the project is created. Its name comes from the project name; hyphens are converted to underscores.
3. The .env file is updated to connect to MariaDB.
4. php artisan migrate --force runs and the tables are created.

If setup fails, Coduva removes the folder and database it created during this process.

Composer "Permission denied" error

On Windows, virus scanning can lock the temporary files that Composer has just written. In this case, Coduva automatically tries the setup once more. If the problem persists, see the Defender advice on the Troubleshooting page.

.env settings

Coduva sets the following values in the .env file:

APP_URL=http://panel.test
DB_CONNECTION=mariadb
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=panel
DB_USERNAME=root
DB_PASSWORD=

If HTTPS is on, APP_URL starts with https://. If the web server or MariaDB runs on a port other than the default, the address and port are written accordingly.

Laravel's web root is the public folder; Coduva configures this itself.

Artisan commands

Open the project screen (click the project's card on the Projects screen; the Laravel tools entry in the left menu lists only Laravel projects) and switch to the Tools tab. The Quick commands card shows commonly used Artisan commands as buttons; the output appears live below the card:

Button	When to use it
artisan migrate	After adding new migrations
artisan optimize:clear	To clear the cache, configuration, route and view caches
artisan key:generate	If APP_KEY is missing from .env
artisan storage:link	To create the public/storage link
artisan route:list	To see the defined routes
artisan about	For a summary of the application and environment

For any other command, switch to the Commands tab. Select artisan as the tool, type the command (e.g. make:model Post -m) and click Run. The same tab has composer and npm tools; the quick command row also contains composer install, composer dump-autoload, npm install and npm run build alongside the Artisan buttons.

Commands run with the project's PHP version. The output is shown live and the exit code is printed when the command finishes.

Processes

On the Processes tab, you can start and stop three long-running processes:

Process	Command
Queue worker	php artisan queue:work
Scheduler	php artisan schedule:work
Vite dev server	npm run dev

Each process shows its status (Running with how long it has been running, or Stopped or Exited with the exit code). The Logs button opens the process output. You can also start and stop the same three processes from the Processes card on the Tools tab. On the Projects screen, the project's card shows how many processes are running for it.

Processes depend on Coduva

Processes run while Coduva is open. Closing the window does not stop them, because Coduva keeps running in the tray. However, when you fully quit Coduva, the project processes are stopped.

Vite requires Node.js. If Coduva's Node is not installed, the system Node is used. See Terminal, Composer and Node.js.

Logs

On the Logs tab, you can select the following sources:

• Nginx error log — web server errors for this project
• Application log — storage/logs/laravel.log
• Output of running or previously run processes

While the tab is open, the log refreshes automatically every few seconds; the Refresh button re-reads it immediately. The full path of the file is shown above the log.

Common errors

Error	Solution
No application encryption key has been specified	Tools → artisan key:generate
SQLSTATE[HY000] [2002]	MariaDB is not running; start it from the Control center. Check DB_PORT in .env
SQLSTATE[HY000] [1049]	The database does not exist; check the DB_DATABASE value or create it from the Database screen
Class "..." not found	Commands → composer install or composer dump-autoload

Coduva also recognizes these errors in the logs itself. See Diagnostics rules.

Next step: To choose a project-specific PHP version, see PHP versions and settings.