Docker

Introduction

Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. AureusERP ships as a single-container production image, so a plain docker run is all it takes — Docker Compose is only used for local development via Laravel Sail.

Database and Storage Persistence

It is recommended to attach named volumes for the database data directory and the application storage directory. This ensures that your data persists even in the case of container failure or termination — even if you destroy the container, your data won't be lost unless you remove the volumes explicitly.

Docker Setup for AureusERP

You can run AureusERP using the pre-configured production image from Docker Hub. It is a single-container, production-ready image that bundles the application, Nginx, PHP-FPM, MySQL, and Supervisor — everything needed to run the ERP with one docker run. AureusERP is fully installed at build time (migrations, seeders, roles & permissions, admin user), so the container boots ready to use.

The image sources live in the docker/production/ directory of the repository, and you can also build it yourself from there:

docker build -t aureuserp:latest docker/production

Local development

The production image is meant for running AureusERP. For local development, use Laravel Sail via the docker-compose.yml at the repository root.

Step 1: Pull the Docker Image

Begin by pulling the AureusERP Docker image with the following command:

docker pull webkul/aureuserp:latest

Step 2: Run the Container

Once the image is pulled, start a new container using the following command:

docker run -d --name aureuserp -p 80:80 \
  -v aureus-mysql:/var/lib/mysql \
  -v aureus-storage:/var/www/aureuserp/storage \
  webkul/aureuserp:latest

Explanation of the Command

• -d: Runs the container in detached mode.
• --name aureuserp: Names the container "aureuserp" for easy reference.
• -p 80:80: Maps port 80 on the host to port 80 in the container (for web access). To use a different host port, change it, e.g. -p 8080:80.
• -v aureus-mysql:/var/lib/mysql: Persists the database files in a named volume.
• -v aureus-storage:/var/www/aureuserp/storage: Persists uploads, logs, and app state.
• webkul/aureuserp:latest: Specifies the latest AureusERP Docker image.

Persistence

Without the named volumes the container is ephemeral — all data is lost on docker rm. Use named volumes (not bind mounts), as an empty bind mount would shadow the pre-installed data. Never expose the MySQL port 3306 publicly.

Local testing over plain HTTP

The image defaults to APP_ENV=production, which forces every generated URL to https — correct for a live site behind TLS. For local testing over plain HTTP, run with -e APP_ENV=local -e APP_URL=http://localhost. The image has no built-in TLS — terminate HTTPS at a reverse proxy in front of the container.

You can override application and database settings at runtime with environment variables such as APP_URL, APP_NAME, APP_TIMEZONE, APP_LOCALE, APP_CURRENCY, and DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME, DB_PASSWORD. Setting DB_HOST to a non-local address switches the container to an external MySQL server and keeps the internal MySQL off. See docker/production/README.md in the repository for the full reference.

Step 3: Verify the Running Container

To check if your container is running, use the command:

docker ps

You should see aureuserp in the list of active containers.

Step 4: Access AureusERP

Open your browser and navigate to:

http://localhost

Or use your server's IP address to access the application.

Step 5: Login

The application is pre-installed, so no setup wizard runs — go to your browser and log in using the following credentials:

Admin Panel Login:

• URL: http://localhost/admin
• Email: admin@example.com
• Password: password

WARNING

Change the admin password immediately after the first login. You can also bake custom credentials into a self-built image with the ADMIN_NAME, ADMIN_EMAIL, and ADMIN_PASSWORD build arguments.

Step 6: Access the Database (Optional)

To connect to the internal MySQL database, use:

docker exec -it aureuserp mysql -u aureus -p aureus

When prompted, enter the password aureus. The internal database name, username, and password are all aureus — they are baked into the image at build time. The DB_DATABASE, DB_USERNAME, and DB_PASSWORD environment variables only apply when connecting to an external database server.

INFO

This works only in internal-database mode. If you started the container with DB_HOST pointing to an external server, the internal MySQL is not running — connect to your external server instead.

If you need to stop the container, run:

docker stop aureuserp

To restart it, use:

docker start aureuserp

Running with Docker (Laravel Sail)

The production image above is meant for running AureusERP. If you want to develop AureusERP — edit its code and see changes live — use the docker-compose.yml at the repository root, powered by Laravel Sail. It runs the full stack in containers without requiring PHP, MySQL, or Redis installed on your machine.

The Compose file defines four services:

Service	Description	Default Port
laravel.test	Application container (PHP 8.4 + web server)	80
mysql	MySQL 8.0 database	3306
redis	Redis cache & queue store	6379
mailpit	Local mail catcher (SMTP + web dashboard)	1025 / 8025

Step 1: Clone and Configure

git clone https://github.com/aureuserp/aureuserp.git
cd aureuserp
cp .env.example .env

By default .env.example is set up for a local (non-Docker) environment. To make the app talk to the containers defined in docker-compose.yml, point the host settings at the service names:

DB_CONNECTION=mysql
DB_HOST=mysql
DB_PORT=3306
DB_DATABASE=aureuserp
DB_USERNAME=sail
DB_PASSWORD=password

REDIS_HOST=redis

MAIL_MAILER=smtp
MAIL_HOST=mailpit
MAIL_PORT=1025

Step 2: Install Dependencies

The Sail image is built from vendor/, so install Composer dependencies first. If you don't have PHP/Composer locally, you can run Composer through a one-off Docker container:

docker run --rm \
    -u "$(id -u):$(id -g)" \
    -v "$(pwd):/var/www/html" \
    -w /var/www/html \
    laravelsail/php84-composer:latest \
    composer install --ignore-platform-reqs

Step 3: Start the Containers

./vendor/bin/sail up -d

TIP

./vendor/bin/sail is a thin wrapper around docker compose. If you prefer, you can run docker compose up -d directly.

Step 4: Generate the App Key & Run the Installation

./vendor/bin/sail artisan key:generate
./vendor/bin/sail artisan erp:install

WARNING

key:generate is only run automatically when scaffolding via composer create-project. Since the steps above use git clone, run it manually before installing — otherwise APP_KEY stays empty and the app will throw encryption errors.

The erp:install command runs migrations and seeders, and prompts for the admin name, email, and password. If it fails with a database connection error on the first try, wait a few seconds for MySQL to finish starting and run it again.

Once the containers are up, the app is available at http://localhost and Mailpit's dashboard at http://localhost:8025.

To stop the containers:

./vendor/bin/sail down

Getting Support

If you encounter any issues or have questions, please contact us at support@aureuserp.com or raise a ticket at AureusERP Support.

Your AureusERP container is now up and running! 🚀