nickbreen / docker-wp-cli Goto Github PK

will require s3cmd (and pip).

apt-get install pip
pip install -g s3cmd

will need to support configuration of IAM credentials too.

Otherwise the rewrite rules are not flushed!

see nickbreen/docker-nginx#2
dupe of #15

At the moment it must be fudged:

environment:
    MYSQL_ENV_MYSQL_ROOT_PASSWORD: xxxxxxxx

just a list of them in an env var ($WP_RAW)

environment:
  WP_RAW: |
    wp rewrite structure "/%post_name%/"
    wp something else

See

• NGINX: http://serverfault.com/a/295791
• Lightly: http://redmine.lighttpd.net/projects/1/wiki/Server_error-handler-404Details

Apache apparently honours whatever the PHP handler returns.

a child theme declares it's parent's "slug" but wp-cli installs a ZIP (without a root directory in the ZIP?) to a generated directory name. E.g.

wp theme install http://www.cherryframework.com/releases/CherryFramework.zip

Contains:

$ unzip -l CherryFramework.zip | head
Archive: CherryFramework.zip
Length Date Time Name

   0  2015-03-27 05:20   admin/
   0  2015-03-27 05:20   admin/css/
3507  2015-03-27 05:20   admin/css/colorpicker.css

24501 2015-03-27 05:20 admin/css/optionsframework.css

And gets installed to (e.g.) themes/CherryFramework-uWHqGv.

Themes are not activated at all. Plugins are all activated in bulk post-installation.

No way to specify which theme and plugins should be activated.

So, add an activate parameter to theme/plugin config lines.

Either use debian:stable|jessie or ubuntun:latest|trusty

Default to the latest version!

Woo API works without mod_disk_cache enabled.

When the module is enabled it borks.

... and

• remove db.php
• enable db check on wp-config (which can create the db)?

It should update the url and title (possibly via wp option update ...).

It should probably also re-set the admin user as per the configuration.

or create a new dockerfile to add it

I.e. bundle theme1234.zip.

How?