Skip to main content

Introduction to Local Development

Introduction to local development with Seravo's Docker environment. Learn how a Docker container simulates the production environment, enabling safe local development with all the necessary tools and optimizations.

Updated this week

Local development allows you to work on your website's code, themes, and plugins safely without affecting the production server. Seravo provides a Docker-based development environment that replicates the Seravo WordPress production environment, saving you time and ensuring compatibility during deployment.

In addition to the core WordPress stack, this environment includes a comprehensive suite of tools for development, debugging, testing, and performance profiling.

How it Works

The environment provides a specialized Docker container pre-equipped with development and management tools. This creates an isolated and identical server setup on your local machine. Unlike a traditional virtual machine, a Docker container is lightweight and starts quickly. Seravo's built-in commands handle the technical setup, allowing you to focus purely on development.

All Seravo projects are designed to be compatible with our Docker environment, allowing you to pull a copy of your production site to your local machine with ease.

Getting Started

To begin developing locally, follow these steps:

  1. Installation: Follow our Docker installation guide to set up the necessary requirements on your local machine.

  2. Configuration: Familiarize yourself with the environment configuration to customize your local setup.

  3. Tools & Commands: Master the commands and tools (such as wp-cli and srv) available within the container to optimize your workflow.

If you encounter any issues during setup or development, please consult our troubleshooting guide for common fixes and instructions on how to report technical problems.

Credentials and URLs

These default credentials and URLs might be different if you have cloned a production site.

WordPress

user: vagrant
​password: vagrant


Adminer

user: vagrant
​password: vagrant


Mailcatcher


Webgrind


Browsersync console


MariaDB

user: root password: root

user: vagrant password: vagrant

Did this answer your question?