Frequently asked questions
Product
Is Coduva paid?
Pricing and the license model have not been finalized yet. Coduva is currently in closed beta. This page will be updated when decisions about the general release are announced. For planned stages, see the Roadmap.
Will there be a macOS or Linux version?
Not in the first year. To focus on Windows-specific issues (ports held by IIS, UAC, the Visual C++ runtime, Defender slowdowns, paths with Turkish characters), Coduva deliberately targets only Windows 10 (22H2) and Windows 11 x64.
Does it use Docker? Will Docker be supported?
No, Coduva does not require Docker. Components run directly on Windows; WSL2 or virtualization is not needed, which is why memory use and file access are lighter. Docker will not be added to the core. In the future (v2), a lightweight bridge for start/stop and log viewing will be considered if the project has a docker-compose.yml.
Can I run Python, Go, Ruby or Node.js applications?
Coduva focuses on PHP. Node.js comes as a managed helper tool for front-end builds (Vite, @wordpress/scripts) in Laravel and WordPress projects. Managing other languages is not planned. Instead, a proxy-type project is planned for v1.x, which would let any application running on a port such as localhost:3000 be reached through a .test address and HTTPS.
Installation and compatibility
Does it work alongside WampServer, XAMPP or Laragon?
Yes. Coduva uses its own directory (C:\Coduva) and does not touch the installations of these programs; it only detects them to warn about port conflicts. If they run at the same time, ports 80 and 3306 conflict. Either stop the other program or change Coduva's ports (for example HTTP 8080, MariaDB 3307). See Ports and the Migration guide.
Why Nginx and not Apache? Will my .htaccess file work?
Coduva 0.2.0 uses Nginx with PHP FastCGI as its web server. Nginx does not read .htaccess files. The basic address routing that WordPress and Laravel need (permalinks, front controller) is already in the configuration Coduva generates. Plugins or applications that depend on custom rules in .htaccess may not work as expected. Apache support is planned for v1.x.
Can I use MySQL?
Coduva ships with MariaDB 11.8 LTS as its database (a single version). MariaDB is compatible with the MySQL drivers used by WordPress and Laravel. MySQL, PostgreSQL and version selection are planned for v1.x. If MySQL is also installed on your computer, port 3306 may conflict; in that case, change Coduva's MariaDB port.
Which PHP versions are supported?
PHP 8.0 and later. With Coduva 0.2.0, PHP 8.3, 8.4 (default) and 8.5 can be installed. Each project can use its own PHP version, and projects using different versions run at the same time. See PHP versions.
Is Xdebug included?
In version 0.2.0, Coduva does not install or configure the Xdebug extension for PHP. A per-project helper to turn Xdebug on and off, and an editor configuration helper, are planned for v1.x. The PHP Debug extension that comes with CodVS also requires a PHP with Xdebug installed.
Does Coduva update itself?
Coduva checks for new versions at most once a day and notifies you, but it does not install them on its own. Installation starts only when you click Install and restart in the Updates card under Settings › Updates, and only packages whose signature has been verified are installed. During the closed beta, the update server is not live yet; you install new versions manually. See Keeping Coduva up to date.
Which code editor does it work with? What is CodVS?
The Editor button on a project page opens the project in CodVS if it is installed, otherwise in Visual Studio Code. CodVS is a separate editor for Coduva projects, based on Code - OSS: it shows Coduva's projects and services, and opens the terminal with the project's PHP version. It is not yet distributed. See CodVS editor.
Everyday use
Why .test? Can I use .local or .dev?
Coduva uses only .test. The .test suffix is reserved for local and testing use (RFC 6761) and never conflicts with a real domain name. .dev is a real top-level domain, and browsers always force it to HTTPS; .local can conflict with mDNS on Windows and network devices.
Where are my files and databases?
| What | Where |
|---|---|
| New projects (default) | C:\Coduva\www\<name> |
| Added projects | In their own folders; Coduva does not move them |
| Database data | C:\Coduva\data\mariadb |
| Database dumps | C:\Coduva\backups\db |
| Settings | %APPDATA%\Coduva\coduva.sqlite |
Full list: Directories and files.
Will my files be deleted if I remove a project?
No. Remove project removes only the record in Coduva, the virtual server, the hosts entry and the project certificate. The project folder and database stay in place. To delete the database, you also need to use the Delete button on the Database screen.
What happens to my projects if I uninstall Coduva?
Your project folders and the data under C:\Coduva (databases, backups) are not deleted automatically. If you want to keep your databases, export them from the Database screen before uninstalling. If you used local HTTPS, also remove the Coduva CA from the Windows certificate store; see Security and privacy.
I closed the window, but the sites are still open. Why?
Closing the window does not close Coduva; Coduva and the services keep running in the system tray. To stop the services, left-click the tray icon and choose Stop all services; to close them together with the application, right-click and choose Stop services and quit. See System tray.
Does Coduva collect data?
No. Coduva does not send telemetry, usage data or error reports, and it does not require an account. Once the components are installed, it works offline. The only regular connection is the update check, made at most once a day; this request carries no identity, version or project information, and it can be turned off on the Settings screen. See Security and privacy.
Can I open the site from my phone or another computer?
In version 0.2.0, no. All services listen only on 127.0.0.1 for security. Sharing the local site through a temporary public address (for showing it to a client, optional) is planned for v2.