Skip to main content

Introduction to Local Development

Explore Seravo's Docker-based local development environment. View built-in developer tools, local URLs, default credentials, and step-by-step instructions to get started.

Local development allows you to build and test WordPress code, themes, and plugins safely on your own computer without affecting your live production site.

For local development, we recommend Seravo's ready-to-use Docker-based development environment, which mirrors Seravo's production servers. Developing in a production-like environment ensures full compatibility and speeds up deployment, as code tested locally works identically in production.

How Does the Development Environment Work?

Seravo's local environment is built around a lightweight Docker container that creates an isolated, production-equivalent server setup directly on your workstation. Unlike a traditional virtual machine, a Docker container starts up quickly and uses minimal system resources.

In addition to WordPress and the PHP/nginx/MariaDB server stack, the container comes pre-installed with Seravo's custom management commands (wp-pull-production-*, wp-watch, wp-test) as well as debugging and performance profiling tools matching the production environment.

Because all Seravo projects follow a unified directory structure (the Seravo/wordpress project template), you can pull a copy of your existing production site onto your local machine with just a few commands.

Getting Started

Follow these steps to set up your local development environment:

  1. Install Docker and the project template: Follow Local Development with Docker to install Docker and spin up your first development container.

  2. Review environment settings: Check Local Environment Configuration if you want to customize your project's local domain (config.yml), PHP version, or other container settings.

  3. Pull content from production: If you are working on an existing site, import your database, plugins, and themes from production by following Pulling a Site to the Development Environment.

  4. Use built-in developer tools: Take advantage of tools inside the container, such as WP-CLI, wp-watch for automatic browser reloads, and Xdebug profiling.

Local URLs and Default Credentials

A fresh local development environment uses wordpress.local as its default domain along with the credentials listed below. If you have configured a custom local domain for your project (such as example.local), replace wordpress.local with your project's local domain.

Service / Tool

URL

Default Credentials

Purpose

WordPress and Admin Dashboard

http://wordpress.local (admin: /wp-admin)

Username: vagrant, password: vagrant

Local WordPress installation and admin dashboard.

Adminer

http://adminer.wordpress.local or http://wordpress.local/.seravo/adminer

Username: vagrant, password: vagrant

Lightweight browser-based tool for managing the MariaDB database.

Mailcatcher

http://mailcatcher.wordpress.local or http://wordpress.local/.seravo/mailcatcher

No login required

Captures all outgoing emails sent by WordPress for safe local testing.

Webgrind

http://webgrind.wordpress.local or http://wordpress.local/.seravo/webgrind

No login required

Web interface for inspecting Xdebug performance profiling reports.

Browsersync Console

http://browsersync.wordpress.local

No login required

Control panel for live reloads while wp-watch is running.

MariaDB Database

localhost (inside the container)

vagrant / vagrant or root / root

Command-line database connections (wp db cli).

Note on Production Copies: When you pull a production database into your local environment (wp-pull-production-db), the local database is overwritten. After pulling, the default vagrant user no longer exists, and you must log in using your production site's user credentials (or create a new local administrator via WP-CLI).

Common Issues and Troubleshooting

  • http://wordpress.local does not open in your browser: First verify that the Docker container is running (docker ps). Also check that your local DNS resolver (dnsmasq) or your workstation's hosts file resolves .local domains to 127.0.0.1.

  • Logging in with the vagrant user fails after importing a database: Pulling a production database replaces local user accounts. Create a new local administrator inside the container by running wp user create developer [email protected] --role=administrator --user_pass=password.

  • The Docker container fails to start due to a port conflict (port is already allocated): Another local web server (such as a local nginx, Apache, or another project's Docker container) is already occupying port 80 or 443 on your machine. Stop conflicting local services before starting the container.

  • The local site redirects to the live production domain: Verify that your local domain is properly set in config.yml and run a search-and-replace on the local database using wp search-replace 'https://production-domain.com' 'http://wordpress.local'.

See Also

A local development container that mirrors your production environment makes testing changes fast and reliable before deploying them live. If you need assistance setting up your local environment or pulling a site into the container, our support team is happy to help at [email protected].

Did this answer your question?