visiblevc/wordpress-starter

A slightly less shitty wordpress development workflow

wordpress-starter's Issues

Make this an automated build on Dockerhub

Happy to help if you're not sure how to go about doing it.

Default Theme + Rest API issue

Hi, great starter by the way! 👍

Just encountering a couple of issues;

1. Is there anyway to make the local test theme (mounted as a volume) set as the active theme by default? On my docker-compose.yml file, I have a local theme (metro-creativex) set but when docker-compose finishes, the default theme is twentyseventeen
2. I've indicated rest-api as a default plugin, but in the plugin checking part, the restful package also gets pulled in which causes a Composer error (see below)

Even just a nudge in the right direction would be helpful, thanks!

docker-compose.yml

version: '2'
services:
  wordpress:
    image: visiblevc/wordpress:latest-php7.0
    ports:
      - 8080:80
      - 443:443
    volumes:
      - ./data:/data # Required if importing an existing database
      - ./wp-content/uploads:/app/wp-content/uploads
      - ./metro-creativex:/app/wp-content/themes/metro-creativex   # Theme development
    environment:
      DB_NAME: wordpress
      DB_PASS: root
      PLUGINS: >-
        [rest-api]https://downloads.wordpress.org/plugin/rest-api.2.0-beta15.zip,
      THEMES: >-
        [local]metro-creativex,
  db:
    image: mariadb:10 # or mysql:5.7
    volumes:
      - data:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: root
volumes:
  data:

run.sh output:

===============================================================================
                         Begin WordPress Installation
===============================================================================
==> Installing WordPress
  -> Downloading... ✓
==> Waiting for MySQL to initialize...
  ->  mysqld is alive
==> Configuring WordPress
  -> Generating wp-config.php file... ✓
==> Checking database
  -> Creating database wordpress ✓
  -> No database backup found. Initializing new database ✓
==> Checking for multisite
  -> Multisite not found. SKIPPING...
==> Checking themes
  -> (1/1) 'metro-creativex' listed as a local volume. SKIPPING...
==> Checking for orphaned themes
  -> 'twentyfifteen' no longer needed. Pruning ✓
Error: No themes deleted.
  -> 'twentyseventeen' no longer needed. Pruning ✘
  -> 'twentysixteen' no longer needed. Pruning ✓
==> Checking plugins
  -> (1/1) 'rest-api' not found. Installing... ✓
  -> (1.5/1) Installing 'restful' WP-CLI package...
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in phar:///usr/local/bin/wp/vendor/composer/composer/src/Composer/DependencyResolver/RuleSetGenerator.php on line 126
✘
==> Checking for orphaned plugins
  -> 'akismet' no longer needed. Pruning... ✓
  -> 'hello' no longer needed. Pruning... ✓
==> Finalizing
  -> Generating .htaccess file ✓
  -> Adjusting file permissions ✓
===============================================================================
                       WordPress Configuration Complete!
===============================================================================
[Wed Dec 07 19:24:44.984603 2016] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.10 (Debian) PHP/7.0.13 configured -- resuming normal operations
[Wed Dec 07 19:24:44.984671 2016] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'

SERVER_NAME undefined when installing Contact Form 7

Overview

• What's your problem about?
  Undefined index: SERVER_NAME error when installing Contact Form 7 plugin via adding contact-form-7 slug to docker-compose.yml. Plugin is installed but the contact forms in the db aren't loaded.
• What is your operating system?
  macOS 10.12.1
• What is your docker version?
  Client/server 1.12.3

docker-compose.yml

      PLUGINS: >-
        contact-form-7,
        jetpack,
        sendgrid-email-delivery-simplified,

docker-compose up output

wordpress_1  | ==> Checking for orphaned themes
wordpress_1  |   -> 'twentyfifteen' no longer needed. Pruning ✓
wordpress_1  |   -> 'twentyfourteen' no longer needed. Pruning ✓
wordpress_1  |   -> 'twentysixteen' no longer needed. Pruning ✓
wordpress_1  | ==> Checking plugins
wordpress_1  |   -> (1/3) 'contact-form-7' not found. Installing... PHP Notice:  Undefined index: SERVER_NAME in /app/wp-content/plugins/contact-form-7/includes/contact-form-template.php on line 98
wordpress_1  | Notice: Undefined index: SERVER_NAME in /app/wp-content/plugins/contact-form-7/includes/contact-form-template.php on line 98
wordpress_1  | PHP Notice:  Undefined index: SERVER_NAME in /app/wp-content/plugins/contact-form-7/includes/functions.php on line 347
wordpress_1  | Notice: Undefined index: SERVER_NAME in /app/wp-content/plugins/contact-form-7/includes/functions.php on line 347
wordpress_1  | PHP Notice:  Undefined index: SERVER_NAME in /app/wp-content/plugins/contact-form-7/includes/contact-form-template.php on line 98
wordpress_1  | Notice: Undefined index: SERVER_NAME in /app/wp-content/plugins/contact-form-7/includes/contact-form-template.php on line 98
wordpress_1  | PHP Notice:  Undefined index: SERVER_NAME in /app/wp-content/plugins/contact-form-7/includes/functions.php on line 347
wordpress_1  | Notice: Undefined index: SERVER_NAME in /app/wp-content/plugins/contact-form-7/includes/functions.php on line 347
wordpress_1  | ✓
wordpress_1  |   -> (2/3) 'jetpack' not found. Installing... ✓
wordpress_1  |   -> (3/3) 'sendgrid-email-delivery-simplified' not found. Installing... ✓
wordpress_1  | ==> Checking for orphaned plugins
wordpress_1  |   -> 'akismet' no longer needed. Pruning... ✓
wordpress_1  |   -> 'hello' no longer needed. Pruning... ✓
wordpress_1  | ==> Finalizing
wordpress_1  |   -> Generating .htaccess file ✓
wordpress_1  |   -> Adjusting file permissions ✓
wordpress_1  | ===============================================================================
wordpress_1  |                        WordPress Configuration Complete!
wordpress_1  | ===============================================================================

Access denied

Hi guys,

I came across your wordpress-starter guide and I wanted to try it out. Though I found that simple running docker-compose up after cloning the repo doesn't seem to "work".

It fails when the database is initialized.

This is the code output, any ideas how to fix this? Because as you can see the project doesn't use the correct address, but I've got no idea where to change it to the correct IP address.

wordpress_1 | => Setup Database:
wordpress_1 | =====================================
wordpress_1 |   Database Host Address:  172.17.0.3
wordpress_1 |   Database Port number:   3306
wordpress_1 |   Database Name:          wordpress
wordpress_1 |   Database Username:      root
wordpress_1 | =====================================
mysql_1     | 2016-01-16T14:00:22.062675Z 2 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
mysql_1     | 2016-01-16T14:00:27.068629Z 3 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
mysql_1     | 2016-01-16T14:00:32.074264Z 4 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
mysql_1     | 2016-01-16T14:00:37.079987Z 5 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
mysql_1     | 2016-01-16T14:00:42.085466Z 6 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
mysql_1     | 2016-01-16T14:00:47.092656Z 7 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
mysql_1     | 2016-01-16T14:00:52.097648Z 8 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
mysql_1     | 2016-01-16T14:00:57.102063Z 9 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
mysql_1     | 2016-01-16T14:01:02.107606Z 10 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
mysql_1     | 2016-01-16T14:01:07.111878Z 11 [Note] Access denied for user 'root'@'172.17.0.2' (using password: YES)
wordpress_1 | Cannot connect to Mysql

Cheers!

Pruning themes and plugins is overzealous

Change 8a10e7a made it so any themes and plugins not defined in the (optional) variables THEMES and PLUGINS variables are deleted. This makes working on local themes and plugins difficult, though it appears that there is a new undocumented [local] tag that one can use to whitelist local plugins.

Since THEMES and PLUGINS are optional, it seems like it'd be better to skip pruning if those variables are not defined. Alternatively, it'd be nice if themes and plugins that are already active in the database restore were not pruned. Thanks.

wp-content folder permission issues

wp-content is root:root

The subfolders are www-data:www-data

When I go into wp-content/ and mkdir themes I get access denied.

Any suggested solutions?

Cannot connect to MySQL

I'm running this as per the instructions in the Getting Started section and I get an error when attempting to connect to the database (see below). I've tried a few different ways to connect to the database but can't see to (e.g. attempting to add a phpmyadmin container). Not sure if this is a local environment issue or not. Any pointers would be greatly appreciated.

Current versions of docker and docker-compose are:
Docker: 1.10.3
Docker-Compose: 1.6.2

Wordpress Log

Wordpress setup!
=> Setup Database:
=====================================
  Database Host Address:  
  Database Port number:   
  Database Name:          wordpress
  Database Username:      root
=====================================
Cannot connect to Mysql

DB Log

2016-03-30T23:00:14.024021Z 0 [Note] mysqld: ready for connections.
Version: '5.7.10'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL

docker-compose.yml

version: '2'
services:
  data:
    image: busybox
    volumes:
      - /app
      - /var/lib/mysql
  wordpress:
    image: visiblevc/wordpress:latest
    links:
      - db
    ports:
      - 8080:80
      - 443:443
    volumes:
      - ./wp-content/uploads:/app/wp-content/uploads
      - ./yourplugin:/app/wp-content/plugins/yourplugin # Plugin development
      - ./yourtheme:/app/wp-content/themes/yourtheme   # Theme development
    environment:
      DB_NAME: wordpress
      DB_PASS: root # must match below
      PLUGINS: >-
        academic-bloggers-toolkit,
        co-authors-plus
      WP_DEBUG: true
  db:
    image: mysql:5.7
    ports:
      - 3306:3306
    volumes:
      - data:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: root
volumes:
  data: {}

404 isn't working

Hi,
I believe it comes from the apache conf that when using permalink as plain, the 404 page isn't caught by wp, but by apache.
Changing to another format (without ?) seems to work tho.

Cannot run wp commands

Tried to run docker-compose run wordpress wp db export /data --allow-root

Getting error: Error: This does not seem to be a WordPress install.

My instances are running while i do this..

Attempt #3 - Can I convince you to enable automatic builds?

@karellm I'm beginning to notice a theme in the Dockerhub repo...

This can be completely solved by enabling automatic builds. Additionally, the README.md from github will stay synced with the Dockerhub readme. It's a win-win.

Dockerfile

Hi,

where is Dockerfile? I can't see it neither in this repository nor on the docker hub. It's no good to pull and install images when you don't know what's inside (= didn't compile it yourself).

Should we consider adding certbot to this image for retrieving/renewing ssl certificates automatically using letsencrypt?

@karellm I'm thinking about actually using this image for production use, but one key component it is lacking is an ability to easily get and renew SSL certs.

Would this be something you think we should add to this?

None writeable permissions with chown /app/wp-content

For some reason Wordpress was still asking for ftp permission to install plugins, when I modified the Dockerfile to chown /app instead it was ok. Any idea why?

gulp `clean` task should also remove generated templates

This would help see which templates are generated (copied by gulp) vs not.

Various build pipeline changes discussion

(See #15 for the beginning of this conversation)

@karellm I'd be happy to collab on this if you'd like. Look over my fork and let me know what you think.

It's also an automated build on Dockerhub

Short on time at the moment, but I'll chime in with a full description of what I changed later on.

Do not include Wordpress in the Docker image

The docker image presently includes Wordpress, causing it to be outdated. We need a way to grab the latest wordpress when we run a container.

Can't install Plugins

I'm getting an error when I try to install plugins. In the theme that I bought, are zip files of 3 plugins. They are showing up in the plugins area after installing the theme, but I get an error when I try to install them.

Error:
The plugin does not have a valid header.
Downloading install package from http://localhost:8080/wp-content/themes/wprentals/libs/plugins/revslider.zip…
Download failed. cURL error 7: Failed to connect to localhost port 8080: Connection refused

Here's my docker-compose.yml file: http://pastebin.com/YhnDvm2S

Preventing links from routing you from development site to actual deployed site?

Hi again,

Still playing around with your image and I can't seem to figure out how one would prevent links from an imported site from navigating to the actual URL (instead of the local url).

For example, the hosted site I would like to work on has an 'about' page at www.mysite.com/about. The links on the local site take me to the actual about page rather than mycontainerip:8080/about.

Any ideas?

ERROR (Line 87): Database creation failed.

I'm running this on a Mac (El Capitan) and using the example docker-compose.yml found on the readme like this:

services:
  wordpress:
    image: visiblevc/wordpress:latest
    links:
      - db
    ports:
      - 8080:80
      - 443:443
    volumes:
      - ./data:/data # Required if importing an existing database
      - ./theme:/app/wp-content/themes/nw-ncs
      #- ./wp-content/uploads:/app/wp-content/uploads
      #- ./yourplugin:/app/wp-content/plugins/yourplugin # Plugin development
      #- ./yourtheme:/app/wp-content/themes/yourtheme   # Theme development
    environment:
      DB_NAME: wordpress
      DB_PASS: root # must match below
      PLUGINS: >-
        akismet,
        hello-dolly
      SEARCH_REPLACE: yoursite.com,localhost:8080
      WP_DEBUG: 'true'
  db:
    image: mysql:5.7
    ports:
      - 3306:3306
    volumes:
      - data:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: root
volumes:
  data: {}

I got an error when I run:

aidrissi:nw-ncs aidrissi$ docker-compose up
Starting nwncs_db_1
Starting nwncs_wordpress_1
Attaching to nwncs_db_1, nwncs_wordpress_1
wordpress_1  | => Waiting for MySQL to initialize... 
wordpress_1  | mysqld is alive
wordpress_1  |  =======================================
wordpress_1  |      Begin WordPress Configuration
wordpress_1  |  =======================================
wordpress_1  | => Generating wp.config.php file... Done!
wordpress_1  | => Create database 'wordpress'... 
wordpress_1  | => ERROR (Line 87): Database creation failed.
nwncs_wordpress_1 exited with code 1

Cannot import my database backup

Overview

Hi,
I can't import my database backup, either through the docker-compose up method (when adding file in project) or though the wp cli command.

Technical informations

OS :

• What is your docker version?

MacBook-Air-de-Laila:wordpress-starter leiluspocus$ docker version
Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 23:26:11 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 23:26:11 2016
 OS/Arch:      linux/amd64

docker-compose.yml

version: '2'
services:
  wordpress:
    image: visiblevc/wordpress:latest
    ports:
      - 8080:80
      - 443:443
    volumes:
      - data:/data
      - ./braxton:/app/wp-content/themes/braxton   # Theme development
    environment:
      DB_NAME: mywebsite
      DB_PASS: root      
      DB_PREFIX: mwb_
      THEMES: >-
        [local]braxton
      SEARCH_REPLACE: local.mywebsite.com,localhost:8080
  db:
    image: mysql:5.7 # or mysql:5.7
    volumes:
      - data:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: root
volumes:
  data: {}

Project structure

MacBook-Air-de-Laila:wordpress-starter leiluspocus$ ls -l
total 104
-rw-r--r--   1 leiluspocus  staff   2001 12 déc 09:38 CHANGELOG.md
-rw-r--r--   1 leiluspocus  staff   1555 12 déc 09:38 ISSUE_TEMPLATE.md
-rw-r--r--   1 leiluspocus  staff   8129 12 déc 09:38 README.md
lrwxr-xr-x   1 leiluspocus  staff     13 12 déc 09:41 braxton -> ../braxton-d/
drwxr-xr-x   4 leiluspocus  staff    136 12 déc 09:41 data
-rw-r--r--   1 leiluspocus  staff    565 12 déc 09:50 docker-compose.yml
-rw-r--r--   1 leiluspocus  staff   5119 12 déc 09:38 gulpfile.js
drwxr-xr-x  27 leiluspocus  staff    918 12 déc 09:40 node_modules
-rw-r--r--   1 leiluspocus  staff   2478 12 déc 10:04 npm-debug.log
-rw-r--r--   1 leiluspocus  staff   1120 12 déc 09:38 package.json
drwxr-xr-x   3 leiluspocus  staff    102 12 déc 09:38 php5.6
drwxr-xr-x   3 leiluspocus  staff    102 12 déc 09:38 php7.0
-rw-r--r--   1 leiluspocus  staff  11494 12 déc 09:38 run.sh

Here is also the content of the data folder :

MacBook-Air-de-Laila:wordpress-starter leiluspocus$ ls -l data
total 4244544
-rwxr-xr-x@ 1 leiluspocus  staff  2173205465 12 déc 09:42 database.sql

docker-compose up output

MacBook-Air-de-Laila:wordpress-starter leiluspocus$ docker-compose up
Creating network "wordpressstarter_default" with the default driver
Creating volume "wordpressstarter_data" with default driver
Pulling db (mysql:5.7)...
5.7: Pulling from library/mysql
386a066cd84a: Pull complete
827c8d62b332: Pull complete
de135f87677c: Pull complete
05822f26ca6e: Pull complete
63ddbddf6165: Pull complete
15fe0fbc587e: Pull complete
93e74acdb291: Pull complete
11c2df82e984: Pull complete
d42a9e6a85c8: Pull complete
e7fb2f3afd87: Pull complete
30724006a583: Pull complete
Digest: sha256:89cc6ff6a7ac9916c3384e864fb04b8ee9415b572f872a2a4cf5b909dbbca81b
Status: Downloaded newer image for mysql:5.7
Pulling wordpress (visiblevc/wordpress:latest)...
latest: Pulling from visiblevc/wordpress
386a066cd84a: Already exists
269e95c6053a: Pull complete
6243d5c57a34: Pull complete
872f6d38a33b: Pull complete
e5ea5361568c: Pull complete
f81f18e77719: Pull complete
f9dbc878ca0c: Pull complete
195935e4100b: Pull complete
935d0c2409b2: Pull complete
d14786710093: Pull complete
b7dff268d83a: Pull complete
d1083150956d: Pull complete
9284aa2927a6: Pull complete
eb710b52f958: Pull complete
78275f047043: Pull complete
63f95fb721a4: Pull complete
488befdcaf6c: Pull complete
Digest: sha256:1e6725c90d85b6cf9b0ce0d94dd393d1a419b5486ae91c5ab2b2bf84ac87b8f3
Status: Downloaded newer image for visiblevc/wordpress:latest
Creating wordpressstarter_db_1
Creating wordpressstarter_wordpress_1
Attaching to wordpressstarter_db_1, wordpressstarter_wordpress_1
wordpress_1  | ===============================================================================
wordpress_1  |                          Begin WordPress Installation
wordpress_1  | ===============================================================================
wordpress_1  | ==> Installing WordPress
db_1         | Initializing database
db_1         | 2016-12-12T09:01:28.435611Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
db_1         | 2016-12-12T09:01:29.485261Z 0 [Warning] InnoDB: New log files created, LSN=45790
db_1         | 2016-12-12T09:01:29.782895Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
db_1         | 2016-12-12T09:01:29.946250Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 9234dc6a-c049-11e6-96f8-0242ac130003.
db_1         | 2016-12-12T09:01:29.979661Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
db_1         | 2016-12-12T09:01:29.982290Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
wordpress_1  |   -> Downloading... ✓
wordpress_1  | ==> Waiting for MySQL to initialize...
db_1         | 2016-12-12T09:01:41.023523Z 1 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:41.023605Z 1 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:41.023640Z 1 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:41.023669Z 1 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:41.024356Z 1 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | Database initialized
db_1         | MySQL init process in progress...
db_1         | 2016-12-12T09:01:47.352413Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
db_1         | 2016-12-12T09:01:47.353805Z 0 [Note] mysqld (mysqld 5.7.16) starting as process 54 ...
db_1         | 2016-12-12T09:01:47.359833Z 0 [Note] InnoDB: PUNCH HOLE support available
db_1         | 2016-12-12T09:01:47.359940Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
db_1         | 2016-12-12T09:01:47.359950Z 0 [Note] InnoDB: Uses event mutexes
db_1         | 2016-12-12T09:01:47.359960Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
db_1         | 2016-12-12T09:01:47.359971Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
db_1         | 2016-12-12T09:01:47.359977Z 0 [Note] InnoDB: Using Linux native AIO
db_1         | 2016-12-12T09:01:47.361204Z 0 [Note] InnoDB: Number of pools: 1
db_1         | 2016-12-12T09:01:47.361440Z 0 [Note] InnoDB: Using CPU crc32 instructions
db_1         | 2016-12-12T09:01:47.365674Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
db_1         | 2016-12-12T09:01:47.392392Z 0 [Note] InnoDB: Completed initialization of buffer pool
db_1         | 2016-12-12T09:01:47.397826Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1         | 2016-12-12T09:01:47.410037Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
db_1         | 2016-12-12T09:01:47.452967Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
db_1         | 2016-12-12T09:01:47.453075Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
db_1         | 2016-12-12T09:01:47.535896Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
db_1         | 2016-12-12T09:01:47.537240Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
db_1         | 2016-12-12T09:01:47.537288Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
db_1         | 2016-12-12T09:01:47.537911Z 0 [Note] InnoDB: Waiting for purge to start
db_1         | 2016-12-12T09:01:47.588575Z 0 [Note] InnoDB: 5.7.16 started; log sequence number 2532794
db_1         | 2016-12-12T09:01:47.590116Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
db_1         | 2016-12-12T09:01:47.591006Z 0 [Note] Plugin 'FEDERATED' is disabled.
db_1         | 2016-12-12T09:01:47.595227Z 0 [Note] InnoDB: Buffer pool(s) load completed at 161212  9:01:47
db_1         | 2016-12-12T09:01:47.602466Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
db_1         | 2016-12-12T09:01:47.635038Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:47.635737Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:47.636318Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:47.636689Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:47.639955Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:47.648600Z 0 [Note] Event Scheduler: Loaded 0 events
db_1         | 2016-12-12T09:01:47.648937Z 0 [Note] mysqld: ready for connections.
db_1         | Version: '5.7.16'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  MySQL Community Server (GPL)
db_1         | Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
db_1         | Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
db_1         | Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
db_1         | 2016-12-12T09:01:53.613558Z 4 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:53.613652Z 4 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:53.613789Z 4 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 
db_1         | 2016-12-12T09:01:53.619587Z 0 [Note] Giving 0 client threads a chance to die gracefully
db_1         | 2016-12-12T09:01:53.620172Z 0 [Note] Shutting down slave threads
db_1         | 2016-12-12T09:01:53.620491Z 0 [Note] Forcefully disconnecting 0 remaining clients
db_1         | 2016-12-12T09:01:53.620779Z 0 [Note] Event Scheduler: Purging the queue. 0 events
db_1         | 2016-12-12T09:01:53.621136Z 0 [Note] Binlog end
db_1         | 2016-12-12T09:01:53.624021Z 0 [Note] Shutting down plugin 'ngram'
db_1         | 2016-12-12T09:01:53.624406Z 0 [Note] Shutting down plugin 'BLACKHOLE'
db_1         | 2016-12-12T09:01:53.624892Z 0 [Note] Shutting down plugin 'partition'
db_1         | 2016-12-12T09:01:53.625099Z 0 [Note] Shutting down plugin 'ARCHIVE'
db_1         | 2016-12-12T09:01:53.625444Z 0 [Note] Shutting down plugin 'MEMORY'
db_1         | 2016-12-12T09:01:53.625640Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
db_1         | 2016-12-12T09:01:53.625820Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
db_1         | 2016-12-12T09:01:53.626009Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
db_1         | 2016-12-12T09:01:53.626255Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
db_1         | 2016-12-12T09:01:53.626443Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
db_1         | 2016-12-12T09:01:53.626581Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
db_1         | 2016-12-12T09:01:53.626814Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
db_1         | 2016-12-12T09:01:53.626963Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
db_1         | 2016-12-12T09:01:53.627089Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
db_1         | 2016-12-12T09:01:53.627225Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
db_1         | 2016-12-12T09:01:53.627539Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
db_1         | 2016-12-12T09:01:53.627759Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
db_1         | 2016-12-12T09:01:53.628229Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
db_1         | 2016-12-12T09:01:53.628423Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
db_1         | 2016-12-12T09:01:53.628581Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
db_1         | 2016-12-12T09:01:53.628721Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
db_1         | 2016-12-12T09:01:53.628971Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
db_1         | 2016-12-12T09:01:53.629566Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
db_1         | 2016-12-12T09:01:53.631096Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
db_1         | 2016-12-12T09:01:53.631243Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
db_1         | 2016-12-12T09:01:53.631359Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
db_1         | 2016-12-12T09:01:53.631416Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
db_1         | 2016-12-12T09:01:53.631513Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
db_1         | 2016-12-12T09:01:53.631572Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
db_1         | 2016-12-12T09:01:53.631674Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
db_1         | 2016-12-12T09:01:53.631730Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
db_1         | 2016-12-12T09:01:53.631824Z 0 [Note] Shutting down plugin 'INNODB_CMP'
db_1         | 2016-12-12T09:01:53.631881Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
db_1         | 2016-12-12T09:01:53.632136Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
db_1         | 2016-12-12T09:01:53.632671Z 0 [Note] Shutting down plugin 'INNODB_TRX'
db_1         | 2016-12-12T09:01:53.632862Z 0 [Note] Shutting down plugin 'InnoDB'
db_1         | 2016-12-12T09:01:54.120137Z 0 [Note] InnoDB: FTS optimize thread exiting.
db_1         | 2016-12-12T09:01:54.121302Z 0 [Note] InnoDB: Starting shutdown...
db_1         | 2016-12-12T09:01:54.222529Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
db_1         | 2016-12-12T09:01:54.224046Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 161212  9:01:54
db_1         | 2016-12-12T09:01:55.990889Z 0 [Note] InnoDB: Shutdown completed; log sequence number 12106150
db_1         | 2016-12-12T09:01:55.993461Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
db_1         | 2016-12-12T09:01:55.993752Z 0 [Note] Shutting down plugin 'MyISAM'
db_1         | 2016-12-12T09:01:55.993921Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
db_1         | 2016-12-12T09:01:55.993968Z 0 [Note] Shutting down plugin 'CSV'
db_1         | 2016-12-12T09:01:55.993995Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
db_1         | 2016-12-12T09:01:55.994134Z 0 [Note] Shutting down plugin 'sha256_password'
db_1         | 2016-12-12T09:01:55.994163Z 0 [Note] Shutting down plugin 'mysql_native_password'
db_1         | 2016-12-12T09:01:55.994644Z 0 [Note] Shutting down plugin 'binlog'
db_1         | 2016-12-12T09:01:55.997406Z 0 [Note] mysqld: Shutdown complete
db_1         | 
db_1         | 
db_1         | MySQL init process done. Ready for start up.
db_1         | 
db_1         | 2016-12-12T09:01:56.294984Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
db_1         | 2016-12-12T09:01:56.296105Z 0 [Note] mysqld (mysqld 5.7.16) starting as process 1 ...
db_1         | 2016-12-12T09:01:56.299685Z 0 [Note] InnoDB: PUNCH HOLE support available
db_1         | 2016-12-12T09:01:56.299728Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
db_1         | 2016-12-12T09:01:56.299740Z 0 [Note] InnoDB: Uses event mutexes
db_1         | 2016-12-12T09:01:56.299747Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
db_1         | 2016-12-12T09:01:56.299753Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
db_1         | 2016-12-12T09:01:56.299758Z 0 [Note] InnoDB: Using Linux native AIO
db_1         | 2016-12-12T09:01:56.300302Z 0 [Note] InnoDB: Number of pools: 1
db_1         | 2016-12-12T09:01:56.300654Z 0 [Note] InnoDB: Using CPU crc32 instructions
db_1         | 2016-12-12T09:01:56.302816Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
db_1         | 2016-12-12T09:01:56.315674Z 0 [Note] InnoDB: Completed initialization of buffer pool
db_1         | 2016-12-12T09:01:56.318584Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1         | 2016-12-12T09:01:56.373396Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
db_1         | 2016-12-12T09:01:56.494724Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
db_1         | 2016-12-12T09:01:56.494852Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
db_1         | 2016-12-12T09:01:56.596765Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
db_1         | 2016-12-12T09:01:56.599294Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
db_1         | 2016-12-12T09:01:56.599357Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
db_1         | 2016-12-12T09:01:56.600252Z 0 [Note] InnoDB: Waiting for purge to start
db_1         | 2016-12-12T09:01:56.652876Z 0 [Note] InnoDB: 5.7.16 started; log sequence number 12106150
db_1         | 2016-12-12T09:01:56.655143Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
db_1         | 2016-12-12T09:01:56.655663Z 0 [Note] Plugin 'FEDERATED' is disabled.
db_1         | 2016-12-12T09:01:56.666452Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
db_1         | 2016-12-12T09:01:56.666453Z 0 [Note] InnoDB: Buffer pool(s) load completed at 161212  9:01:56
db_1         | 2016-12-12T09:01:56.668618Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
db_1         | 2016-12-12T09:01:56.669202Z 0 [Note] IPv6 is available.
db_1         | 2016-12-12T09:01:56.669555Z 0 [Note]   - '::' resolves to '::';
db_1         | 2016-12-12T09:01:56.669746Z 0 [Note] Server socket created on IP: '::'.
db_1         | 2016-12-12T09:01:56.701390Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:56.701883Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:56.710872Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-12-12T09:01:56.717366Z 0 [Note] Event Scheduler: Loaded 0 events
db_1         | 2016-12-12T09:01:56.717693Z 0 [Note] mysqld: ready for connections.
db_1         | Version: '5.7.16'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
wordpress_1  |   ->  mysqld is alive
wordpress_1  | ==> Configuring WordPress
wordpress_1  |   -> Generating wp-config.php file... ✓
wordpress_1  | ==> Checking database
wordpress_1  |   -> Creating database mywebsite ✓
wordpress_1  |   -> No database backup found. Initializing new database ✓

Import output through wp cli

I did a npm install at the root of the folder before running the command.

MacBook-Air-de-Laila:wordpress-starter leiluspocus$ npm run wp db import /data/database.sql

> [email protected] wp /Users/lailaatrmouh/Work/wordpress-starter
> wpcmd() { docker exec $(docker ps -lq) /bin/bash -c "sudo -u www-data wp $(echo $@)"; };wpcmd  "db" "import" "/data/database.sql"

/bin/bash: sudo: command not found

npm ERR! Darwin 15.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "wp" "db" "import" "/data/database.sql"
npm ERR! node v4.4.7
npm ERR! npm  v2.15.8
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] wp: `wpcmd() { docker exec $(docker ps -lq) /bin/bash -c "sudo -u www-data wp $(echo $@)"; };wpcmd  "db" "import" "/data/database.sql"`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] wp script 'wpcmd() { docker exec $(docker ps -lq) /bin/bash -c "sudo -u www-data wp $(echo $@)"; };wpcmd  "db" "import" "/data/database.sql"'.
npm ERR! This is most likely a problem with the visible-wordpress package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     wpcmd() { docker exec $(docker ps -lq) /bin/bash -c "sudo -u www-data wp $(echo $@)"; };wpcmd  "db" "import" "/data/database.sql"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs visible-wordpress
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! 
npm ERR!     npm owner ls visible-wordpress
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/lailaatrmouh/Work/wordpress-starter/npm-debug.log

Please let me know if you need any more information.

docker-compose up doesn't finish.

I did just what I was told to, cloned git and did docker-compose up.
I didn't touch docker-compose.yml at all.
Lots of message started appearing and it goes to like below.

...
wordpress_1 | => Removing unneeded themes... Done!
wordpress_1 | => Installing needed themes... Done!
wordpress_1 | =======================================
wordpress_1 | WordPress Configuration Complete!
wordpress_1 | =======================================

and it just stops from then.
I waited for like an hour but nothing happens.
Tried to open localhost:8000 but of course, nothing opens.

I did it at both windows10 and OSX El Capitain and stops at the same position.
Is it just me?

`docker-compose up` fails

Overview

• What's your problem about?

Initial docker-compose up fails with error.

• What is your operating system?

macOS Sierra 10.12.1 (16B2555)

• What is your docker version?

Docker version 1.12.3, build 6b644ec

Getting started

# copy the files
git clone https://github.com/visiblevc/wordpress-starter.git
rm -rf .git Dockerfile run.sh README.md CHANGELOG.md ISSUE_TEMPLATE.md

# start the website at localhost:8080
docker-compose up

docker-compose up output

Pulling wordpress (visiblevc/wordpress:php7.0)...
Pulling repository docker.io/visiblevc/wordpress
ERROR: Tag php7.0 not found in repository docker.io/visiblevc/wordpress

Development or productive image?

Hey there, I read your wordpress development blog post and set up this environment on my box.

I am quite happy with it (There are some possible tweaks in the scripts that I will look into later) but there is one thing that bugs me. In my comprehension, this is clearly an image with development in mind, not productive usage. So, for security/privacy reasons, I would (and did it here) only open the ports on my local machine, like

wordpress:
  ports:
      - 127.0.0.1:80:80
      - 127.0.0.1:443:443

and

mysql:
  ports:
    - 127.0.0.1:3306:3306

because, by default having mysql running on default port with root:root authentication makes me feel sick.

I think, in order to have docker images that can be used for developments "as is" they should be as closed down as possible, if one needs more, they need to configure it explicitly (Can be mentioned in the documentation, though).

Making it easier to tweak php.ini

Hi guys, and thanks a lot for this project! I hadn't done WordPress development for some years and it seems you brought a bit of sanity to this old world 👍

I needed to adjust some variables in php.ini to increase upload size on my website. I tried to modify the dockerfile both in the php5.6 and php7.0 directories, but that didn't work. I googled my problem and found a comment in a separate project that helped me a lot: docker-library/wordpress#10 (comment)

I figured it could be helpful for you to provide a tweaks.ini file at the root of the starter, and add the following line in the default docker-compose.yml, or instructions in the Readme.

volumes:
      - data:/data
      - ./tweaks.ini:/usr/local/etc/php/conf.d/tweaks.ini

What do you think?
Thanks.

gulp deploy-assets ( gulp-clean unable to delete )

The command gulp deploy-assets runs into an error where the gulp-clean plugin is unable to delete.

Suggestion: add Composer to the image

Having PHP's Composer pre-installed in the image and adding a 'REQUIREproperty in thedocker-compose.yml` would be a very nice addition to this project I believe.

I'd like to use wordpress-starter to unit-test a plugin of mine. Having Composer pre-installed would allow me to quickly install PHPUnit and test my plugin.

I might give a PR a try, but I'd prefer to be sure that it has a chance of being accepted.

Thank you in advance :-)

It should be possible to specify the version of themes and plugins installed from wordpress.org

There's a very good reason why most package managers out there (e.g. NPM, Composer, Docker Hub) make it a good practice of explicitly specifying the version of dependencies: that's because newer versions of dependencies can (and often will) break your project.

wp-cli makes it possible to specify theme and plugin versions. Wordpress starter should not become a dependency manager, but being able to use this feature would be a welcome addition to the tool I believe.

I'm willing to send a PR :-)

Why removing .git, Dockerfile and run.sh?

Thanks for sharing this project! Has some great improvements over "normal" wordpress template development (that's why I would want to use this project)...

I have a question though, the readme file states that you should invoke 'rm -rf .git Dockerfile run.sh' to delete a couple of files. Why is that, it doen't seem necessary?

Many errors...

Hello,

I had many erros when docker-compose :

ERROR: for db driver failed programming external connectivity on endpoint theproject_db_1 (a74f76838da5608a454e97444153b2cb15bf79e8bf2250805140f1f25e0f33d6): Error starting userland proxy: listen tcp 0.0.0.0:3306: bind: address already in use
Traceback (most recent call last):
File "/usr/local/container-station/python/bin/.libs/docker-compose", line 9, in
load_entry_point('docker-compose==1.7.1', 'console_scripts', 'docker-compose')()
File "/share/CACHEDEV1_DATA/.qpkg/container-station/usr/local/container-station/python/lib/python2.7/site-packages/compose/cli/main.py", line 63, in main
log.error(e.msg)
AttributeError: 'ProjectError' object has no attribute 'msg'
[/home/my/the-project] # docker-compose up
Creating theproject_db_1

ERROR: for db driver failed programming external connectivity on endpoint theproject_db_1 (b98f59ebecb5c63f439d34c8a4b0475cdf380b26ca6b19a92f31927ff3701958): Error starting userland proxy: listen tcp 0.0.0.0:3306: bind: address already in use
Traceback (most recent call last):
File "/usr/local/container-station/python/bin/.libs/docker-compose", line 9, in
load_entry_point('docker-compose==1.7.1', 'console_scripts', 'docker-compose')()
File "/share/CACHEDEV1_DATA/.qpkg/container-station/usr/local/container-station/python/lib/python2.7/site-packages/compose/cli/main.py", line 63, in main
log.error(e.msg)
AttributeError: 'ProjectError' object has no attribute 'msg'

ANY IDEAS ??!!
Thank you !

Wordpress not installed?

I'm new to Docker, so apologies if there is something I am doing wrong / stupid! I really like the look of the docker setup you have here but I seem to get errors with installing WordPress

I've deleted the image and tried a few times now, with the same result.

docker-compose up halts after database setup

Running Docker on Windows 10 using the Docker Toolbox https://www.docker.com/docker-toolbox

When running docker-compose up it starts ok until it creates the databse at which point the script appears to get stuck. Last output lines included below:

�[33mmysql_1     | �[0mVersion: '5.7.9'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
�[36mtheproject_data_1 exited with code 0
�[0m�[32mwordpress_1 | �[0mDownloading WordPress 4.4 (en_US)...
�[32mwordpress_1 | �[0mSuccess: WordPress downloaded.
�[32mwordpress_1 | �[0m  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
�[32mwordpress_1 | �[0m                                 Dload  Upload   Total   Spent    Left  Speed
100   768    0   768    0     0    851      0 --:--:-- --:--:-- --:--:--   850
�[32mwordpress_1 | �[0mWordpress setup!
�[32mwordpress_1 | �[0m=> Setup Database:
�[32mwordpress_1 | �[0m=====================================
�[32mwordpress_1 | �[0m  Database Host Address:  172.17.0.2
�[32mwordpress_1 | �[0m  Database Port number:   3306
�[32mwordpress_1 | �[0m  Database Name:          wordpress
�[32mwordpress_1 | �[0m  Database Username:      root
�[32mwordpress_1 | �[0m=====================================
�[32mwordpress_1 | �[0m=> Creating database wordpress
�[32mwordpress_1 | �[0mDatabase setup!

Know why it would be getting stuck here and/or encountered this before?

Working with WP plugins

Is there an easy way to automatically activate plugins?

Main issue is when ever I try to run wp-cli commands on the machine with command: in the docker-compose.yml it runs before everything is good to go.

So if I was to add command: wp plugin activate --all I get the following output:

wordpress_1 | Error: This does not seem to be a WordPress install.
wordpress_1 | Pass --path=`path/to/wordpress` or run `wp core download`.

I might have missed something here, so happy for some guidance.

Gulpfile typo's/inconsistencies

Thanks for these articles! Looking forward to the next parts, it's been very helpful so far.

There are a few mistakes in the Gulpfile;

• The tasks compile-styles and compile-scripts are later called as compile-css and compile-js by gulp.watch
• gulp.watch looks in /sass/ while compile-styles looks in /scss/
• in part 2 of the series it says to create a wp-content/themes/the-theme/assets/js folder but the Gulpfile looks in /scripts/

Production build stuck waiting for MySQL to initialize (GKE & kubernetes)

Overview

I'm trying to deploy this image with Google Container Engine (https://cloud.google.com/container-engine/docs/tutorials/hello-wordpress), but it seems to get stuck on initialising MySQL.

kubernetes pod log output

wordpress_1  | ===============================================================================
wordpress_1  |                          Begin WordPress Installation
wordpress_1  | ===============================================================================
wordpress_1  | ==> Installing wordpress
wordpress_1  |   -> Downloading... ✓
wordpress_1  | ==> Waiting for MySQL to initialize...

Serialized string replace?

Does the string replace also handle serialized arrays?

Export command doesn't work

Export command fails for me:

$ docker-compose run wordpress wp db export /data --allow-root
Error: This does not seem to be a WordPress install.
Pass --path=`path/to/wordpress` or run `wp core download`.

If I run a docker run inside wordpress container then it works:

$ docker exec -it wordpress_wordpress_1 wp db export /data/wordpress.sql --allow-root

For instance, I've tried to do a ls -l with this two ways with different results:

$ docker-compose run wordpress ls -l
total 24
-rw-r--r-- 1 root root  1202 Jul  8  2015 index.php
-rw-r--r-- 1 root root 12586 Jul  8  2015 logo.png
drwxr-xr-x 4 root root  4096 Sep 24 16:52 wp-content

$ docker exec -it wordpress_wordpress_1 ls -l
total 208
-rw-r--r--  1 www-data www-data   418 Sep 24 11:05 index.php
-rw-r--r--  1 www-data www-data 19935 Sep 24 11:05 license.txt
-rw-r--r--  1 www-data www-data 12586 Jul  8  2015 logo.png
-rw-r--r--  1 www-data www-data  7344 Sep 24 11:05 readme.html
-rw-r--r--  1 www-data www-data  5456 Sep 24 11:05 wp-activate.php
drwxr-xr-x  9 www-data www-data  4096 Sep 24 11:05 wp-admin
-rw-r--r--  1 www-data www-data   364 Sep 24 11:05 wp-blog-header.php
-rw-r--r--  1 www-data www-data   413 Sep 24 15:42 wp-cli.yml
-rw-r--r--  1 www-data www-data  1477 Sep 24 11:05 wp-comments-post.php
-rw-r--r--  1 www-data www-data  2853 Sep 24 11:05 wp-config-sample.php
-rw-r--r--  1 www-data www-data  1625 Sep 24 15:42 wp-config.php
drwxr-xr-x  7 www-data www-data  4096 Sep 24 16:13 wp-content
-rw-r--r--  1 www-data www-data  3286 Sep 24 11:05 wp-cron.php
drwxr-xr-x 17 www-data www-data 12288 Sep 24 11:05 wp-includes
-rw-r--r--  1 www-data www-data  2382 Sep 24 11:05 wp-links-opml.php
-rw-r--r--  1 www-data www-data  3353 Sep 24 11:05 wp-load.php
-rw-r--r--  1 www-data www-data 34057 Sep 24 11:05 wp-login.php
-rw-r--r--  1 www-data www-data  7786 Sep 24 11:05 wp-mail.php
-rw-r--r--  1 www-data www-data 13920 Sep 24 11:05 wp-settings.php
-rw-r--r--  1 www-data www-data 29890 Sep 24 11:05 wp-signup.php
-rw-r--r--  1 www-data www-data  4035 Sep 24 11:05 wp-trackback.php
-rw-r--r--  1 www-data www-data  3064 Sep 24 11:05 xmlrpc.php

I'm running docker for mac 1.12.1.

My docker-compose.yml is like the one in f7ae79e but with an additional phpMyadmin container.

plugins / themes tagged with [local] raise yaml error when first entry

not working docker-compose.yml

services:
  wordpress:
    image: visiblevc/wordpress:latest
    links:
      - db
    ports:
      - 8080:80
      - 443:443
    volumes:
      - ./data:/data
      - ./wp-content/themes/mytheme:/app/wp-content/themes/mytheme
      - ./wp-content/plugins/myplugin:/app/wp-content/plugins/myplugin
    environment:
      DB_NAME: wordpress
      DB_PASS: root
      THEMES: [local]mytheme
      PLUGINS: [local]myplugin
  db:
    image: mysql:5.7 # or mariadb:10
    ports:
      - 3306:3306
    volumes:
      - data:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: root
volumes:
  data: {}

error on bash

$ docker-compose up 
ERROR: yaml.parser.ParserError: while parsing a block mapping
  in "./docker-compose.yml", line 15, column 7
expected <block end>, but found '<scalar>'
  in "./docker-compose.yml", line 17, column 22

working docker-compose.yml

services:
  wordpress:
    image: visiblevc/wordpress:latest
    links:
      - db
    ports:
      - 8080:80
      - 443:443
    volumes:
      - ./data:/data
      - ./wp-content/themes/mytheme:/app/wp-content/themes/mytheme
      - ./wp-content/plugins/myplugin:/app/wp-content/plugins/myplugin
    environment:
      DB_NAME: wordpress
      DB_PASS: root
      THEMES: twentysixteen, [local]mytheme
      PLUGINS: piklist, [local]myplugin
  db:
    image: mysql:5.7 # or mariadb:10
    ports:
      - 3306:3306
    volumes:
      - data:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: root
volumes:
  data: {}

Overview

• What's your problem about?
  annoying yaml error
• What is your operating system?
  debian stretch
• What is your docker version? docker version

docker version
Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 21:45:16 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 21:45:16 2016
 OS/Arch:      linux/amd64

SoapClient is missing on 0.12.1

Hi,

First I wanna thank you so much !! I'm using this project with WooCommerce plugin so far, and it's helping us a lot to simplify the environment setup. You guys rock!!!

Today we updated our local docker image to latest (0.12.1), and we noticed our WP plugin stopped working. We just realized that the PHP SoapClient is missing on latest version, but it's present until 0.11.0. WooCommerce also makes that check on System Status page.

I believe that's an important dependency to be present on all versions, please check if it's possible to be added on next version.

BR

Where is the "Auto deploy your site on your server" article? :-)

Hi @karellm,

I've been playing with this project for two days and discovered that the article/docs on how to get a project in production doesn't exist yet. Is there a draft somewhere? I'm quite new to Docker and don't quite know where to start.
Any help would be greatly appreciated.

Best regards,
Louis-Rémi

ERROR (Line 120): Could not generate .htaccess file.

Steps to Reproduce

1. clone repo
2. remove files as directed
3. place db.sql in data/
4. docker-compose up

Result:

Creating network "devdocker_default" with the default driver
Creating volume "devdocker_data" with default driver
Pulling db (mysql:5.7)...
5.7: Pulling from library/mysql
5c90d4a2d1a8: Already exists
89e2627e9201: Pull complete
76f6983b0fe0: Pull complete
653577605512: Pull complete
bd6c32d9a05f: Pull complete
0632c43d2f8e: Pull complete
e76bc01eb91c: Pull complete
c7fb4d78a4d6: Pull complete
438c1fb96f64: Pull complete
f3ed22f2810a: Pull complete
b836883cb3d9: Pull complete
Digest: sha256:a9a5b559f8821fe73d58c3606c812d1c044868d42c63817fa5125fd9d8b7b539
Status: Downloaded newer image for mysql:5.7
Pulling wordpress (visiblevc/wordpress:latest)...
latest: Pulling from visiblevc/wordpress
6ffe5d2d6a97: Pull complete
f4e00f994fd4: Pull complete
e99f3d1fc87b: Pull complete
a3ed95caeb02: Pull complete
c10ab9e629d8: Pull complete
5c65b067601c: Pull complete
2cbc3ddde9c1: Pull complete
9a5e857e989f: Pull complete
7bd95ceec22a: Pull complete
c27094051f1e: Pull complete
d820ec68d287: Pull complete
10876575da90: Pull complete
c52bfb2aab51: Pull complete
Digest: sha256:2e885a62c77145d901e2aa156790718e79ad5957a4624fe3bcdcd94b72f79ec1
Status: Downloaded newer image for visiblevc/wordpress:latest
Creating devdocker_db_1
Creating devdocker_wordpress_1
Attaching to devdocker_db_1, devdocker_wordpress_1
db_1         | Initializing database
db_1         | 2016-08-01T10:11:57.081813Z 0 [Warning] InnoDB: New log files created, LSN=45790
db_1         | 2016-08-01T10:11:57.369834Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
db_1         | 2016-08-01T10:11:57.439963Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 610c763f-57d0-11e6-8bd5-0242ac120002.
db_1         | 2016-08-01T10:11:57.444359Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
db_1         | 2016-08-01T10:11:57.445929Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
db_1         | 2016-08-01T10:11:58.145189Z 1 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:11:58.145283Z 1 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:11:58.145332Z 1 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:11:58.145404Z 1 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:11:58.146341Z 1 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | Database initialized
db_1         | MySQL init process in progress...
db_1         | 2016-08-01T10:11:59.888587Z 0 [Note] mysqld (mysqld 5.7.13) starting as process 48 ...
db_1         | 2016-08-01T10:11:59.892902Z 0 [Note] InnoDB: PUNCH HOLE support available
db_1         | 2016-08-01T10:11:59.893029Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
db_1         | 2016-08-01T10:11:59.893041Z 0 [Note] InnoDB: Uses event mutexes
db_1         | 2016-08-01T10:11:59.893057Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
db_1         | 2016-08-01T10:11:59.893114Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
db_1         | 2016-08-01T10:11:59.893133Z 0 [Note] InnoDB: Using Linux native AIO
db_1         | 2016-08-01T10:11:59.893450Z 0 [Note] InnoDB: Number of pools: 1
db_1         | 2016-08-01T10:11:59.893579Z 0 [Note] InnoDB: Using CPU crc32 instructions
db_1         | 2016-08-01T10:11:59.895320Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
db_1         | 2016-08-01T10:11:59.902960Z 0 [Note] InnoDB: Completed initialization of buffer pool
db_1         | 2016-08-01T10:11:59.912443Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1         | 2016-08-01T10:11:59.920794Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
db_1         | 2016-08-01T10:11:59.938277Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
db_1         | 2016-08-01T10:11:59.938429Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
db_1         | 2016-08-01T10:12:00.174498Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
db_1         | 2016-08-01T10:12:00.176296Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
db_1         | 2016-08-01T10:12:00.176472Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
db_1         | 2016-08-01T10:12:00.177684Z 0 [Note] InnoDB: Waiting for purge to start
db_1         | 2016-08-01T10:12:00.228156Z 0 [Note] InnoDB: 5.7.13 started; log sequence number 2523957
db_1         | 2016-08-01T10:12:00.228718Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
db_1         | 2016-08-01T10:12:00.229174Z 0 [Note] Plugin 'FEDERATED' is disabled.
db_1         | 2016-08-01T10:12:00.232031Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
db_1         | 2016-08-01T10:12:00.233426Z 0 [Note] InnoDB: Buffer pool(s) load completed at 160801 10:12:00
db_1         | 2016-08-01T10:12:00.238197Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:00.238252Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:00.238276Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:00.238296Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:00.241108Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:00.254235Z 0 [Note] Event Scheduler: Loaded 0 events
db_1         | 2016-08-01T10:12:00.255289Z 0 [Note] mysqld: ready for connections.
db_1         | Version: '5.7.13'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  MySQL Community Server (GPL)
db_1         | Warning: Unable to load '/usr/share/zoneinfo/Factory' as time zone. Skipping it.
db_1         | Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
db_1         | Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
db_1         | Warning: Unable to load '/usr/share/zoneinfo/posix/Factory' as time zone. Skipping it.
db_1         | Warning: Unable to load '/usr/share/zoneinfo/right/Factory' as time zone. Skipping it.
db_1         | Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
db_1         | 2016-08-01T10:12:04.306998Z 4 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:04.307031Z 4 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:04.307298Z 4 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 
db_1         | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
db_1         | 
db_1         | 2016-08-01T10:12:04.310918Z 0 [Note] Giving 0 client threads a chance to die gracefully
db_1         | 2016-08-01T10:12:04.311033Z 0 [Note] Shutting down slave threads
db_1         | 2016-08-01T10:12:04.311053Z 0 [Note] Forcefully disconnecting 0 remaining clients
db_1         | 2016-08-01T10:12:04.311161Z 0 [Note] Event Scheduler: Purging the queue. 0 events
db_1         | 2016-08-01T10:12:04.311451Z 0 [Note] Binlog end
db_1         | 2016-08-01T10:12:04.313229Z 0 [Note] Shutting down plugin 'ngram'
db_1         | 2016-08-01T10:12:04.313256Z 0 [Note] Shutting down plugin 'BLACKHOLE'
db_1         | 2016-08-01T10:12:04.313262Z 0 [Note] Shutting down plugin 'partition'
db_1         | 2016-08-01T10:12:04.313265Z 0 [Note] Shutting down plugin 'ARCHIVE'
db_1         | 2016-08-01T10:12:04.313269Z 0 [Note] Shutting down plugin 'MEMORY'
db_1         | 2016-08-01T10:12:04.313276Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
db_1         | 2016-08-01T10:12:04.313995Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
db_1         | 2016-08-01T10:12:04.315114Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
db_1         | 2016-08-01T10:12:04.315345Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
db_1         | 2016-08-01T10:12:04.315361Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
db_1         | 2016-08-01T10:12:04.315365Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
db_1         | 2016-08-01T10:12:04.315368Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
db_1         | 2016-08-01T10:12:04.315372Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
db_1         | 2016-08-01T10:12:04.315375Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
db_1         | 2016-08-01T10:12:04.315379Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
db_1         | 2016-08-01T10:12:04.315382Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
db_1         | 2016-08-01T10:12:04.315386Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
db_1         | 2016-08-01T10:12:04.315389Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
db_1         | 2016-08-01T10:12:04.315392Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
db_1         | 2016-08-01T10:12:04.315396Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
db_1         | 2016-08-01T10:12:04.315400Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
db_1         | 2016-08-01T10:12:04.315805Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
db_1         | 2016-08-01T10:12:04.315810Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
db_1         | 2016-08-01T10:12:04.315819Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
db_1         | 2016-08-01T10:12:04.315823Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
db_1         | 2016-08-01T10:12:04.315827Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
db_1         | 2016-08-01T10:12:04.315830Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
db_1         | 2016-08-01T10:12:04.316247Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
db_1         | 2016-08-01T10:12:04.316257Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
db_1         | 2016-08-01T10:12:04.316262Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
db_1         | 2016-08-01T10:12:04.316266Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
db_1         | 2016-08-01T10:12:04.316269Z 0 [Note] Shutting down plugin 'INNODB_CMP'
db_1         | 2016-08-01T10:12:04.316273Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
db_1         | 2016-08-01T10:12:04.316276Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
db_1         | 2016-08-01T10:12:04.316280Z 0 [Note] Shutting down plugin 'INNODB_TRX'
db_1         | 2016-08-01T10:12:04.316284Z 0 [Note] Shutting down plugin 'InnoDB'
db_1         | 2016-08-01T10:12:04.316708Z 0 [Note] InnoDB: FTS optimize thread exiting.
db_1         | 2016-08-01T10:12:04.317662Z 0 [Note] InnoDB: Starting shutdown...
db_1         | 2016-08-01T10:12:04.420742Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
db_1         | 2016-08-01T10:12:04.421374Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 160801 10:12:04
db_1         | 2016-08-01T10:12:06.052188Z 0 [Note] InnoDB: Shutdown completed; log sequence number 12129534
db_1         | 2016-08-01T10:12:06.054921Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
db_1         | 2016-08-01T10:12:06.054955Z 0 [Note] Shutting down plugin 'MyISAM'
db_1         | 2016-08-01T10:12:06.054968Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
db_1         | 2016-08-01T10:12:06.054973Z 0 [Note] Shutting down plugin 'CSV'
db_1         | 2016-08-01T10:12:06.054978Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
db_1         | 2016-08-01T10:12:06.054998Z 0 [Note] Shutting down plugin 'sha256_password'
db_1         | 2016-08-01T10:12:06.055028Z 0 [Note] Shutting down plugin 'mysql_native_password'
db_1         | 2016-08-01T10:12:06.055136Z 0 [Note] Shutting down plugin 'binlog'
db_1         | 2016-08-01T10:12:06.055795Z 0 [Note] mysqld: Shutdown complete
db_1         | 
db_1         | 
db_1         | MySQL init process done. Ready for start up.
db_1         | 
db_1         | 2016-08-01T10:12:06.362082Z 0 [Note] mysqld (mysqld 5.7.13) starting as process 1 ...
db_1         | 2016-08-01T10:12:06.369337Z 0 [Note] InnoDB: PUNCH HOLE support available
db_1         | 2016-08-01T10:12:06.369481Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
db_1         | 2016-08-01T10:12:06.369503Z 0 [Note] InnoDB: Uses event mutexes
db_1         | 2016-08-01T10:12:06.369663Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
db_1         | 2016-08-01T10:12:06.369930Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
db_1         | 2016-08-01T10:12:06.370082Z 0 [Note] InnoDB: Using Linux native AIO
db_1         | 2016-08-01T10:12:06.370781Z 0 [Note] InnoDB: Number of pools: 1
db_1         | 2016-08-01T10:12:06.371044Z 0 [Note] InnoDB: Using CPU crc32 instructions
db_1         | 2016-08-01T10:12:06.374573Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
db_1         | 2016-08-01T10:12:06.383467Z 0 [Note] InnoDB: Completed initialization of buffer pool
db_1         | 2016-08-01T10:12:06.385417Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1         | 2016-08-01T10:12:06.398248Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
db_1         | 2016-08-01T10:12:06.411515Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
db_1         | 2016-08-01T10:12:06.411680Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
db_1         | 2016-08-01T10:12:06.475474Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
db_1         | 2016-08-01T10:12:06.477008Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
db_1         | 2016-08-01T10:12:06.477059Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
db_1         | 2016-08-01T10:12:06.477995Z 0 [Note] InnoDB: Waiting for purge to start
db_1         | 2016-08-01T10:12:06.528775Z 0 [Note] InnoDB: 5.7.13 started; log sequence number 12129534
db_1         | 2016-08-01T10:12:06.529180Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
db_1         | 2016-08-01T10:12:06.533349Z 0 [Note] Plugin 'FEDERATED' is disabled.
db_1         | 2016-08-01T10:12:06.541167Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
db_1         | 2016-08-01T10:12:06.541583Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
db_1         | 2016-08-01T10:12:06.541878Z 0 [Note] IPv6 is available.
db_1         | 2016-08-01T10:12:06.542119Z 0 [Note]   - '::' resolves to '::';
db_1         | 2016-08-01T10:12:06.542301Z 0 [Note] Server socket created on IP: '::'.
db_1         | 2016-08-01T10:12:06.542373Z 0 [Note] InnoDB: Buffer pool(s) load completed at 160801 10:12:06
db_1         | 2016-08-01T10:12:06.547787Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:06.548155Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:06.551001Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-08-01T10:12:06.558200Z 0 [Note] Event Scheduler: Loaded 0 events
db_1         | 2016-08-01T10:12:06.558819Z 0 [Note] mysqld: ready for connections.
db_1         | Version: '5.7.13'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
wordpress_1  | => Downloading wordpress... Done!
wordpress_1  | => Waiting for MySQL to initialize... 
wordpress_1  | mysqld is alive
wordpress_1  |  =======================================
wordpress_1  |      Begin WordPress Configuration
wordpress_1  |  =======================================
wordpress_1  | => Generating wp.config.php file... Done!
wordpress_1  | => Create database 'wordpress'... Done!
wordpress_1  | => Loading data backup from /data/ig613.sql... Done!
wordpress_1  | => Generating .htaccess file... 
wordpress_1  | => ERROR (Line 120): Could not generate .htaccess file.
devdocker_wordpress_1 exited with code 1

Running docker on windows 10 using docker-machine

Hi, this is a great project and I think it's just what I was looking for.

I run docker-compose up but then when I visit
http://192.168.99.100:8080/
there are a lot of resources that fail to load from http://localhost:8080/.

Any help be appreciated.
Thanks in advance.

Is it possible to run modified version of run.sh on starting container?

Hi,

This is really good and I learning to make use of docker. I am trying to use this for my plugin development workflow. I usually work with wordpress multisite and so was trying to see if there is a way to override the default run.sh file while executes while starting the container.

I have tried using the command: in docker-compose.yml but no luck. Or is there a way you could create a postrun.sh file which by default is empty but a user can fill it up with all custom commands he wishes to execute after the container in up and running.

I also tried running the docker exec $(docker ps -lq) /bin/bash -c "wp core multisite-convert --allow-root" however that sometimes works and sometimes doesn't really respond (not sure why). I use Docker for Mac.

Thanks,
Neel

scripts/install-plugins.sh no output?

Me again :). When I run docker-compose run wordpress /scripts/install-plugins.sh I get no output in the terminal and no changes on my filesystem. I'm using boot2docker with MyBoot2docker in Windows 10. Any ideas what I could be doing wrong?

"Stylesheet is missing" on installing existing theme.

Hello!
I am following the instructions here: https://visible.vc/engineering/docker-environment-for-wordpress/

and I have run into an issue where I'm installing an existing theme, i've pointed to said theme in the docker compose yml file, and I go to start my instance. It has the theme in there, but I get a "stylesheet is missing" in the description and it's in the "Broken Themes" section.

I'm somewhat of a noob at this, so I'm sure it might just be something elementary. Any help you could give would be greatly appreciated.

Thanks!
Josh

Email in local development

Hey there

just using your main docker image, and trying to test email sending but with no joy, any suggestions?

Flew

@dsifford I got contact by the guys behind this: https://local.getflywheel.com/

Thought I would share, it looks interesting.

Setup accommodations for HTTPS

Overview

I am trying to get an existing WordPress site's theme and database running in Docker, for local development.

The existing (live) site is served via HTTPS. The site's WordPress Address (URL) is set to https://www.homesforheroes.com - so the protocol is stored in the WP database.

I can get WordPress working fine, if I don't import the database. However, I need the database imported for development purposes.

So I am importing the production site's database, following your examples, and that seems to be working (tables are visible on the mysql container), however...

When I try to load to the site on my host machine (at http://localhost:8080), I get redirected to https://localhost:8080/ but WordPress doesn't load. Instead, I get the following message in Chrome:

This site can’t provide a secure connection
localhost sent an invalid response.
Try running Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR

Host OS: macOS Sierra
Docker version 1.12.1, build 6f9534c
docker-compose version 1.8.0, build f3628c7

I have tried adjusting the ports of the wordpress container, as well as adjusting the SEARCH_REPLACE strings, to no avail. Although, I am a relative noob when it comes to Docker, sysadmin, and port forwarding, so it is most definitely possible that the changes I attempted were incorrect.

Is there something obvious that I'm missing, either in the port setup, the `SEARCH_REPLACE', or elsewhere? Any tips? Thanks in advance.

docker-compose.yml

version: '2'
services:
  wordpress:
    image: visiblevc/wordpress:latest
    links:
      - db
    ports:
      - 8080:80
      - 443:443
    volumes:
      - ./data:/data
      - ./wp-content/themes/enfold:/app/wp-content/themes/enfold
      - ./wp-content/uploads:/app/wp-content/uploads
    environment:
      DB_NAME: wordpress
      DB_PASS: root # must match db:environment:MYSQL_ROOT_PASSWORD below
      DB_PREFIX: hfh_
      PLUGINS: >-
        advanced-custom-fields,
        css-hero,
        css-plus,
        header-footer,
        redirection,
        timeline-express,
        wordpress-seo,
      SEARCH_REPLACE: https://www.homesforheroes.com,http://localhost:8080
      WP_DEBUG: 'true'
  db:
    image: mysql:5.7
    ports:
      - 3306:3306
    volumes:
      - data:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: root
volumes:
  data: {}

Project structure

/data
  /database.sql
/wp-content
  /themes
    /enfold
.editorconfig
.gitignore
docker-compose.yml
Dockerfile
gulpfile.js
package.json
run.sh

docker-compose up output

Creating homesforheroescom_db_1
Creating homesforheroescom_wordpress_1
Attaching to homesforheroescom_db_1, homesforheroescom_wordpress_1
db_1         | 2016-10-27T19:48:19.077424Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
db_1         | 2016-10-27T19:48:19.081194Z 0 [Note] mysqld (mysqld 5.7.16) starting as process 1 ...
db_1         | 2016-10-27T19:48:19.089431Z 0 [Note] InnoDB: PUNCH HOLE support available
db_1         | 2016-10-27T19:48:19.089491Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
db_1         | 2016-10-27T19:48:19.089504Z 0 [Note] InnoDB: Uses event mutexes
db_1         | 2016-10-27T19:48:19.089517Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
db_1         | 2016-10-27T19:48:19.089545Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
db_1         | 2016-10-27T19:48:19.089556Z 0 [Note] InnoDB: Using Linux native AIO
db_1         | 2016-10-27T19:48:19.089995Z 0 [Note] InnoDB: Number of pools: 1
db_1         | 2016-10-27T19:48:19.090156Z 0 [Note] InnoDB: Using CPU crc32 instructions
db_1         | 2016-10-27T19:48:19.094560Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
db_1         | 2016-10-27T19:48:19.109649Z 0 [Note] InnoDB: Completed initialization of buffer pool
db_1         | 2016-10-27T19:48:19.113006Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1         | 2016-10-27T19:48:19.132581Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
db_1         | 2016-10-27T19:48:19.252556Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
db_1         | 2016-10-27T19:48:19.253563Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
db_1         | 2016-10-27T19:48:19.677205Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
db_1         | 2016-10-27T19:48:19.679760Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
db_1         | 2016-10-27T19:48:19.679921Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
db_1         | 2016-10-27T19:48:19.681078Z 0 [Note] InnoDB: 5.7.16 started; log sequence number 26805051
db_1         | 2016-10-27T19:48:19.681737Z 0 [Note] Plugin 'FEDERATED' is disabled.
db_1         | 2016-10-27T19:48:19.684611Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
db_1         | 2016-10-27T19:48:19.692721Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
db_1         | 2016-10-27T19:48:19.694904Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
db_1         | 2016-10-27T19:48:19.695352Z 0 [Note] IPv6 is available.
wordpress_1  | ===============================================================================
wordpress_1  |                          Begin WordPress Installation
wordpress_1  | ===============================================================================
db_1         | 2016-10-27T19:48:19.695494Z 0 [Note]   - '::' resolves to '::';
db_1         | 2016-10-27T19:48:19.695833Z 0 [Note] Server socket created on IP: '::'.
db_1         | 2016-10-27T19:48:19.696357Z 0 [Note] InnoDB: Buffer pool(s) load completed at 161027 19:48:19
db_1         | 2016-10-27T19:48:19.884580Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-10-27T19:48:19.884877Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-10-27T19:48:19.908121Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
db_1         | 2016-10-27T19:48:19.918407Z 0 [Note] Event Scheduler: Loaded 0 events
db_1         | 2016-10-27T19:48:19.919039Z 0 [Note] mysqld: ready for connections.
db_1         | Version: '5.7.16'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
wordpress_1  | ==> Installing WordPress
wordpress_1  |   -> Downloading... ✓
wordpress_1  | ==> Waiting for MySQL to initialize...
wordpress_1  |   ->  mysqld is alive
wordpress_1  | ==> Configuring WordPress
wordpress_1  |   -> Generating wp-config.php file... ✓
wordpress_1  | ==> Checking database
wordpress_1  |   -> Database exists. SKIPPING...
wordpress_1  | ==> Checking for multisite
wordpress_1  |   -> Multisite not found. SKIPPING...
wordpress_1  | ==> Checking themes
wordpress_1  |   -> No theme dependencies listed
wordpress_1  | ==> Checking for orphaned themes
wordpress_1  |   -> 'twentyfifteen' no longer needed. Pruning ✓
wordpress_1  |   -> 'twentyfourteen' no longer needed. Pruning ✓
wordpress_1  | ==> Checking plugins
wordpress_1  |   -> (1/7) 'advanced-custom-fields' not found. Installing... ✓
wordpress_1  |   -> (2/7) 'css-hero' not found. Installing... ✓
wordpress_1  |   -> (3/7) 'css-plus' not found. Installing... ✓
wordpress_1  |   -> (4/7) 'header-footer' not found. Installing... ✓
wordpress_1  |   -> (5/7) 'redirection' not found. Installing... ✓
wordpress_1  |   -> (6/7) 'timeline-express' not found. Installing... ✓
wordpress_1  |   -> (7/7) 'wordpress-seo' not found. Installing... ✓
wordpress_1  | ==> Checking for orphaned plugins
wordpress_1  |   -> 'akismet' no longer needed. Pruning... ✓
wordpress_1  |   -> 'hello' no longer needed. Pruning... ✓
wordpress_1  | ==> Finalizing
wordpress_1  |   -> Generating .htaccess file ✓
wordpress_1  |   -> Adjusting file permissions ✓
wordpress_1  | ===============================================================================
wordpress_1  |                        WordPress Configuration Complete!
wordpress_1  | ===============================================================================

wp-content/uploads permission denied when uploading media

O+G are root:root not www-data:www-data How are you guy's handling this?

Dockerfile conflict + outdated(?) shell script

Hi there.

First of all, excellent base image! I read your associated blog post and the way you have this set up is extremely clever.

Some issues I'm having are the following...

1. The install-plugins shell script you have in this repository is outdated and does not work. I think this line needs to be updated to this....

curl -LOk# https://downloads.wordpress.org/plugin/${plugin}.zip

1. Is the Dockerfile in this repo the same as the one used in your dockerhub image? The reason I ask is because I can cleanly install wordpress using your dockerhub image, but I can not do the same if I fork this repo, and change the image: visiblecv/wordpress line in the docker-compose.yml file to build: .. Could this an error on my end?

Thanks for the help!

Add option to environment variables to specify database prefix

See #32 (comment)