WordPress site

Coduva installs a working WordPress site in one step: core files, database, wp-config.php and an admin account. Afterwards, the common tasks are on the Tools tab of the project screen.

New WordPress project

Before you start, make sure the services are running. If MariaDB is not running, Coduva starts it for you during setup.

1. Click Projects → New project (or Ctrl+K → Create new project).
2. Select WordPress as the template; the dialog opens with this template.
3. Enter a Project name, e.g. magaza. The address becomes magaza.test.
4. The Location line shows the project folder (C:\Coduva\www\magaza). To use a different parent folder, click Change. The folder must be empty if it already exists.
5. Optionally, choose a PHP version and check the Use HTTPS box.
6. Click Create.

During setup, each step is shown live:

1. The latest Turkish version of WordPress is downloaded and the SHA-1 value of the file is verified.
2. A database dedicated to the project is created. Its name comes from the project name; hyphens are converted to underscores (musteri-sitesi → musteri_sitesi).
3. The wp-config.php file is written with the MariaDB connection details.
4. WordPress is installed and an admin account is created.

This process requires an internet connection. If setup fails partway, Coduva removes the folder and database it created during this process; it does not leave a half-finished site behind.

WordPress admin account

When setup finishes, the window shows the message "magaza.test is ready", the site address and the WordPress admin account box, together with the Open site button:

Field	Value
User	admin
Password	A randomly generated 16-character password

The password is shown only once

Coduva does not save the password anywhere. If you want, copy it now with the Copy link next to it. If you do not save it, that is fine: you can always log in to the site with the Log in as admin button on the Tools tab.

The admin email address is set to admin@magaza.test, and no setup email is sent.

Database connection

Coduva writes the following values to wp-config.php:

define( 'DB_NAME', 'magaza' );
define( 'DB_USER', 'root' );
define( 'DB_PASSWORD', '' );
define( 'DB_HOST', '127.0.0.1:3306' );

If you change the MariaDB port, the port in DB_HOST must also be updated to the new value. If you see the message "Error establishing a database connection", this is the first place to check.

Tools tab

Open the project screen (click the project's card on the Projects screen) and switch to the Tools tab. The WordPress tools entry in the left menu lists only WordPress projects; you can also reach the project from there.

The tab has three cards: one-click login, debugging and URL replacement.

One-click admin login

The Log in as admin button opens the admin panel in the browser and logs you in as admin without asking for a password.

The link is single-use and valid for 2 minutes. For this, Coduva uses a small plugin at wp-content/mu-plugins/coduva-login.php; it generates a new token each time.

Debugging (WP_DEBUG)

Use the button on the Debugging (WP_DEBUG) line to turn debugging on and off. When it is on, Coduva sets the following constants in wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Errors are not shown on the page; they are written to wp-content/debug.log. You can read this file with the Application log option on the Logs tab.

Change URL (search-replace)

WordPress stores the site address in many places in the database. When you move a site from another address (for example, from a live server or from http://localhost/magaza) to Coduva, these addresses must be changed. A plain SQL find-and-replace corrupts serialized data, so Coduva uses the search-replace command of WP-CLI instead.

1. Enter the old address in the Old text field, e.g. https://www.magaza.com. The field is pre-filled with the project's address in Coduva (http://magaza.test); for a site you moved from elsewhere, replace it with the address of the old site.
2. Enter the new address in the New text field, e.g. http://magaza.test.
3. First click Dry run. Coduva changes nothing and lists, below the card, which tables would change and how many changes each would have.
4. If the result is what you expect, click Apply.

The operation runs across all tables and reports only the rows that changed (wp search-replace --all-tables --precise --report-changed-only).

Tip

Before you make the change, take a copy of the database: on the Database screen, click Export. See Working with databases.

WP-CLI commands

WP-CLI comes bundled with Coduva. You can run commands from two places.

Commands tab: Select wp as the tool, type the command (e.g. plugin install akismet) and click Run. The output is shown live; when it finishes, the exit code is printed. Quick command buttons:

• wp plugin list
• wp theme list
• wp cache flush
• wp core version
• wp core update

The same row also has composer install, composer dump-autoload, npm install and npm run build buttons; in the tool list, composer and npm can also be selected alongside wp.

Project terminal: The Terminal button on the project screen opens a command window where the wp command is ready to use:

wp plugin install woocommerce --activate
wp user list
wp option get siteurl

See Terminal, Composer and Node.js.

Permalinks and .htaccess

Coduva uses Nginx as its web server. Nginx does not read .htaccess files; Coduva's configuration redirects addresses that are not found to index.php. This way, WordPress permalinks work without any extra setup.

Redirect rules that plugins write into .htaccess are not applied by Nginx. Apache support is planned for v1.x.

Next step: If the site requires HTTPS, go to the Local HTTPS page.