WordPress Stack for Coolify (Docker Compose)

A complete WordPress stack for Coolify with MariaDB database, FileBrowser for file management, and Adminer for database administration. This stack is meant to be deployed and managed via Coolify—do not run docker-compose directly; use Coolify’s UI and workflows instead.

📦 What's Included

This Coolify Docker Compose stack includes four services:

1. WordPress (wordpress:latest)

• The main WordPress CMS application
• Connected to MariaDB database
• Persistent file storage via Docker volume
• Health checks to ensure service availability

2. MariaDB (mariadb:11)

• MySQL-compatible database server
• Dedicated WordPress database
• Persistent data storage
• Automatic health monitoring

3. FileBrowser (filebrowser/filebrowser:latest) 🔑

• Web-based file manager for WordPress files
• Direct access to WordPress installation files
• Allows editing, uploading, and managing files through a web interface
• Persistent configuration and database storage

4. Adminer (adminer:latest)

• Lightweight database management interface
• Dark theme enabled (pepa-linha-dark)
• Pre-configured to connect to MariaDB
• Alternative to phpMyAdmin

---

⚠️ IMPORTANT: Stop FileBrowser and Adminer After Build

Once you have finished building and configuring your website, stop the FileBrowser and Adminer containers in Coolify to increase security.

• FileBrowser gives direct access to your WordPress files and is a high-risk target if left exposed.
• Adminer gives full database access and should not remain running in production.

In Coolify: open your stack → stop the FileBrowser and Adminer services. You can start them again temporarily when you need to manage files or the database, then stop them when done.

---

🔐 Getting FileBrowser Credentials

IMPORTANT: FileBrowser creates default credentials on first startup. You MUST retrieve these from the FileBrowser container logs in Coolify.

How to get the credentials in Coolify

1. In Coolify, open your project and the WordPress stack (Docker Compose application).

2. Find the FileBrowser service/container.

3. Open Logs for that container (e.g. “Container logs” or “Logs” tab).

4. Look for lines similar to:

   Using database: /database/filebrowser.db
   Creating new database
   Username: admin
   Password: PASSWORD AUTOGENERATE -> Check the Container logs
   

• Username: always admin.
• Password: autogenerated on first startup—you must get it from the FileBrowser container logs in Coolify (project → stack → FileBrowser service → Logs). Look for the line that shows the generated password.

📊 Adminer Database Access

To access your WordPress database through Adminer:

1. Open Adminer in your browser
2. Use these credentials:
   • System: MySQL
   • Server: mariadb
   • Username: Value from SERVICE_USER_WORDPRESS
   • Password: Value from SERVICE_PASSWORD_WORDPRESS
   • Database: wordpress

🗂️ Docker Volumes

The stack uses four persistent volumes (managed by Coolify):

• wordpress-files: WordPress installation files (accessible via FileBrowser)
• mariadb-data: Database files
• filebrowser-config: FileBrowser configuration
• filebrowser-database: FileBrowser user database

📄 License

This configuration is provided as-is for use with open-source software components. Each service maintains its own license:

• WordPress: GPLv2 or later
• MariaDB: GPLv2
• FileBrowser: Apache License 2.0
• Adminer: Apache License 2.0 or GPL 2

🤝 Contributing

Feel free to submit issues or pull requests to improve this stack configuration.