Download the PHP package lch/docker-wordpress without Composer

On this page you can find all versions of the php package lch/docker-wordpress. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of lch/docker-wordpress

Informations about the package docker-wordpress

Docker WordPress Boilerplate (Apache, PHP-FPM, MariaDB, WP-CLI, phpMyAdmin)

Latest tag

A ready-to-start Docker boilerplate for WordPress projects with:

Quick Start

Create a new project from this template:

Without a version constraint, Composer installs the latest stable release.

If you want HEAD of main, use:

Then go into your project directory and update .env.

Prerequisites

Install just

Use your preferred package manager:

If your distro package is unavailable/outdated, use cargo install just.

Install envsubst

On macOS:

On most Linux distros, envsubst is provided by gettext.

Configuration (.env)

Set all values before first initialization.

Directories

Runtime

Host Mapping

WordPress

GitHub (used by just install-and-version)

Database

Ports

Usage

List available recipes:

Initial project setup

This recipe:

Day-to-day commands

Maintenance commands

set-divi-api-key writes Divi update credentials to the WordPress option et_automatic_updates_options using WP-CLI. warmup-updates emulates authenticated back-office page loads (/${BO_URL}/) + front-office hits + cron triggers to refresh update metadata (same effect as manual BO/FO navigation). update-themes and update-plugins call this warmup automatically before applying updates (THEME_UPDATE_RECHECK_PASSES / PLUGIN_UPDATE_RECHECK_PASSES). Core recipes can execute optional hooks when present:

Private Just overlays

The root justfile can optionally import extra local files:

Role of this feature:

These files are ignored by git via justfile.*.

Example:

Repository bootstrap helper

install-and-version assumes you are authenticated with GitHub CLI (gh auth login), bootstraps WordPress/GitHub/Git on first run, and skips GitHub bootstrap if the local git repo is already initialized.

Tools (tools/)

The tools/ directory contains helper scripts that are not part of the main just workflow.

check_wordpress_state.py

This script compares a local WordPress instance against production and returns a non-zero exit code only when a blocking mismatch is detected.

What it checks:

Files:

Recommended workflow:

  1. Make sure the local stack is up and the site is reachable.
  2. Run the checker in the mode that matches your migration/update context.
  3. Review the SUMMARY block first, then inspect page-level details only if the summary is WARN or FAIL.
  4. If needed, rerun with explicit paths for the pages that matter most to the project.

Basic usage:

Usage with a project .env:

Usage with a JSON config file:

Configuration sources are resolved in this order: CLI options, JSON config, environment variables, then script defaults.

Supported environment variables:

Important behavior:

Recommended modes:

Examples:

Output format:

How to read the metrics:

Status semantics:

Exit codes:

Access URLs

Reset From Scratch

  1. Stop containers:

  2. Remove WordPress files and DB data using the paths configured in .env.
  3. Re-run initialization:

For full test reset (including remote GitHub repo deletion), use:

Notes

All versions of docker-wordpress with dependencies

PHP Build Version
Package Version
No informations.
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package lch/docker-wordpress contains the following files

Loading the files please wait ...