Download the PHP package dbtlr/wp-docker-dev without Composer

On this page you can find all versions of the php package dbtlr/wp-docker-dev. 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?

Informations about the package wp-docker-dev

WordPress Docker Development Enviorment

Quick Start

This assumes you have Composer installed locally to help orchastrate local tools.

This will create a new wp-site directory, download the dependencies, and will also ask you a series of questions that are used to build a .env file which will be used to configure your Docker deploy.

Here's an example of the .env file that is created:

Yous should also add an entry to your /etc/hosts file that maps the DOMAIN above to 127.0.0.1

If you're running multiple Docker instances, then change the IP_ROOT to another number, i.e. 172.16.201 to avoid conflicts.

Launch Docker Compose

Once you see Command line: 'apache2 -D FOREGROUND' has completed, you should be able to navigate to http://$DOMAIN in your web browser.

If you wish to run Docker in the background, use

In order to halt a Docker container running in the background, instead use:

Your files

In the src/ directory you'll find 3 folders:

These are read-only mounts that you're able to update, but that the Docker container cannot change. This is done by default so that you handle maintaining your files using source control and not allow WordPress to accidently destory your work through its own automated install process.

Consider managing your plugins and themes using WPackagist instead. For your convenience, the basic composer configuration is included.

All versions of wp-docker-dev with dependencies

PHP Build Version
Package Version
Requires php Version >=7.1
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 dbtlr/wp-docker-dev contains the following files

Loading the files please wait ....