/laravel_react_google_demo

Primary LanguagePHPMIT LicenseMIT

Generic Webapp Docker Setup

This docker config is meant primarily for local development prototyping. NOT MEANT FOR PRODUCTION. The mysql config exposes its port to the host so that you can run scripts like wordmove or even manually load/dump/debug. I primarily use this config repo for WordPress, but can be used for any PHP-based web app.

nginx's default.conf doesn't read from environment variables, so I set the local URL to wordpress.local

Dependencies

Install the following dependencies through their respective installation instructions:

  • docker
  • docker-machine
  • docker-compose
  • wordmove
  • wp-cli

Dotenv

Included is a .env_sample file. Since Docker and Wordmove utilize dotenv, it's convenient to define all environment variables there.

Web App Setup

Initialize Docker

  1. Make sure your Docker machine is running: docker-machine start
  2. After you have an IP provisioned (usually 192.168.99.100), load the docker machine environment variables eval `docker-machine env`
  3. Copy the .env_sample into a file .env and provide values. Note that DC_DB_NAME and LOCAL_DB_NAME should be the same, but it is provided separately for debugging purposes.
  4. Edit your Windows/Mac/Linux 'hosts' file to point the url worpdress.local to the IP address provisioned by your docker machine. LOCAL_DB_LOCATION should be set to worpdress.local for this reason.
  5. Then fire up your docker images docker-compose up -d (I have issues with Linux and need sudo to provision volumes/ports)

Initialize Your Web Files

The webroot folder can hold any PHP files you want. The following command installs WordPress without default plugins/themes: wp core download --path=webroot --skip-content

Configuring WordPress

You can now go to wordpress.local in your browser. You can set the location of your Database Host to the value database because Docker's DNS resolver configures the name as provided in docker-compose.yml.

Note that rsync_options in the Movefile is set to --no-perms --no-owner --no-group this means that rysnc will ignore permission changes in your webroot directory. This makes local development a little safer because it prevents forgotten permission 'fixes'

Have Fun

Star this repo if you want.