Adding an existing project

If you already have a project folder, you do not need to move it into Coduva. With Add folder, you turn the folder into a project where it is; Coduva assigns it a .test address and a virtual host.

Adding a folder

1. On the Projects screen, click Add folder (or Ctrl+K → Add folder as project).
2. Select the project folder with Choose folder.
3. Coduva inspects the folder and suggests the following:
   • Detected type: WordPress, Laravel or PHP
   • Web root: the folder the browser will open
   • Project name: generated from the folder name
4. If needed, change the name, choose a PHP version and check the Use HTTPS box.
5. Click Add and grant the UAC approval for the hosts file.

When the project is ready, a "name.test is ready" notification appears in the lower right corner. If the hosts file cannot be updated, the project is still added, and the notification says "The project was added but the hosts file could not be updated"; retry from the Local domains screen.

The project name is generated automatically from the folder name: Turkish characters are simplified, and spaces and other symbols are turned into hyphens. For example, for a folder named Müşteri Sitesi, musteri-sitesi is suggested; the address becomes musteri-sitesi.test.

How is the type detected?

Type	Condition	Web root
WordPress	The folder contains wp-config.php, or contains both wp-load.php and a wp-includes folder	The project folder
Laravel	The folder contains an artisan file and composer.json mentions laravel/framework	public
PHP	None of the above	public if public/index.php exists; otherwise the project folder

The type determines which tools appear on the project screen: for WordPress projects, WP-CLI and WordPress tools; for Laravel projects, Artisan and processes. Plain PHP projects have no Tools tab; the Commands tab offers composer and npm, and the Processes tab offers Vite.

Database connection

When you add a folder, Coduva does not create a new database, and it does not change the project's wp-config.php or .env file. If the project comes from another server, you need to import its database and update the connection details. For a step-by-step guide, see Migrating from WampServer, XAMPP or Laragon.

Paths with non-ASCII characters

If the folder path contains a non-ASCII character (for example, C:\Users\Gökhan\Masaüstü\site), Coduva shows this warning: "The folder path contains non-ASCII characters; some PHP tools may have problems."

The project is still added and usually works, but Composer, WP-CLI or some PHP extensions may fail on such paths. If possible, move the project to an ASCII path such as C:\Coduva\www.

Changing the web root

If Coduva's guess is wrong (for example, your site is served from a public_html or web folder):

1. On the Projects screen, click the project's card; the project screen opens on the General tab.
2. Click Change on the Web root line.
3. Select the correct folder.

Coduva refreshes the Nginx configuration and reloads the web server without interruption.

Apps that run on their own port (proxy)

Tools such as Node.js, Vite and Next.js run on their own port (for example, localhost:3000). To give such an app a .test address and HTTPS, add the project as a proxy. This feature arrives with Coduva 0.3.0.

1. On the Projects screen, click Add folder and select the app's folder.
2. Tick Forward to a port (proxy).
3. In App port, enter the port your app listens on (for example, 3000).
4. Tick Use HTTPS if you want it, then click Add.

Coduva forwards requests for project.test to 127.0.0.1:3000. Live-reload (WebSocket) connections are forwarded too. PHP is not used for this project.

Coduva does not start the app; start it yourself from the terminal that the Terminal button on the project screen opens (for example, npm run dev). If the app is not running, the browser shows a 502 error.

To change the port later, use the App port field on the project screen's General tab. The ports of Nginx, MariaDB and the PHP pool (9800–9999) cannot be used as a target.

Project settings

On the General tab, you can change the following project settings at any time:

• PHP version — see PHP versions and settings
• Node.js version — see Terminal, Composer and Node.js
• Use HTTPS (toggle) — see Local HTTPS

Each change is saved immediately and a "Saved" notification appears. On the same tab, the Project folder, Web root and linked Database details are also shown.

At the top of the project screen, there are badges for the address (copied with the button next to it), type, PHP version, HTTPS and database, along with the Folder, Editor, Terminal and Open site buttons. The same shortcuts are also available on the Projects screen from the ⋯ menu on the card (along with Copy address and Details). Editor opens the project in CodVS first, or in Visual Studio Code if CodVS is not available, or in File Explorer if neither is available. See CodVS.

Project archive (0.3.0)

You can pack a project's files, database and settings into a single file and open it on this computer or on another computer with Coduva installed. This feature arrives with Coduva 0.3.0.

To archive:

1. On the project screen's General tab, click Archive on the Project archive card.
2. Coduva writes the archive to C:\Coduva\backups\projects as name-date.coduva.zip and shows its path.

The archive contains the whole project folder, a dump of the linked database and the project settings (type, PHP version, web root, HTTPS). The node_modules folder is not included; npm install brings it back after opening. MariaDB must be running for the database dump.

To open:

1. On the Projects screen, click Open archive and select the .coduva.zip file.
2. Change the project name and location if needed. If a project with the same name exists, you must enter another name.
3. Click Open.

Coduva extracts the files, imports the database and prepares the .test address. If the address changed (a different name or port), addresses in the WordPress database are converted, and for Laravel the APP_URL and database settings in .env are updated. If the archive's PHP version is not installed, the project opens with the default PHP version. If opening fails, the created folder and database are rolled back.

An archive can contain secrets

The archive includes .env, wp-config.php and the entire database. Share the file only with people you trust.

Removing a project

1. On the project screen, click Remove project below the General tab.
2. In the "Remove magaza?" dialog, read what will be removed and click Remove.

Coduva removes the virtual host, the name.test address, the certificate and the running project processes.

Your files and database are safe

Removing a project does not delete the project files or the database. The folder stays where it is, and the database remains visible on the Database screen. If you also want to delete the database, you must do so separately from the Database screen.

If you delete or move the project folder outside Coduva, the project's card on the Projects screen shows a "Project folder not found" warning. Put the folder back, or remove the project and add it again.

Next step: If you are moving from another local server, follow the migration guide.