chriszarate / docker-wordpress-vip Goto Github PK

Hi Chris, and thanks for your work on this.

I'm not a frequent WordPress developer, so I may be missing something obvious but the wordpress/wordpress user does not appear to have super admin privileges. Is there a way to add a SA or promote the default user?

Edit: I should mention, I tried:

docker-compose exec wordpress wp super-admin add wordpress

which results in:

PHP Warning:  in_array() expects parameter 2 to be array, string given in phar:///usr/local/bin/wp-cli/php/commands/super-admin.php on line 110
PHP Stack trace:
PHP   1. {main}() /usr/local/bin/wp-cli:0
PHP   2. include() /usr/local/bin/wp-cli:4
PHP   3. include() phar:///usr/local/bin/wp-cli/php/boot-phar.php:5
PHP   4. WP_CLI\Runner->start() phar:///usr/local/bin/wp-cli/php/wp-cli.php:21
PHP   5. WP_CLI\Runner->_run_command() phar:///usr/local/bin/wp-cli/php/WP_CLI/Runner.php:906
PHP   6. WP_CLI\Runner->run_command() phar:///usr/local/bin/wp-cli/php/WP_CLI/Runner.php:319
PHP   7. WP_CLI\Dispatcher\Subcommand->invoke() phar:///usr/local/bin/wp-cli/php/WP_CLI/Runner.php:312
PHP   8. call_user_func:{phar:///usr/local/bin/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php:372}() phar:///usr/local/bin/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php:372
PHP   9. WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}() phar:///usr/local/bin/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php:372
PHP  10. call_user_func:{phar:///usr/local/bin/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php:67}() phar:///usr/local/bin/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php:67
PHP  11. Super_Admin_Command->add() phar:///usr/local/bin/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php:67
PHP  12. in_array() phar:///usr/local/bin/wp-cli/php/commands/super-admin.php:110
No changes.

Google owns the .dev TLD, it'd be best to switch to the .test TLD as it's protected by an RFC, and Google and making modifications to chromium to enforce internal standards on .dev sites

$ docker-compose up

dockerwordpressvip_mysql_1 is up-to-date
dockerwordpressvip_mysql_phpunit_1 is up-to-date
Starting dockerwordpressvip_proxy_1
Starting dockerwordpressvip_lib_1
Recreating dockerwordpressvip_wordpress_1

ERROR: for proxy Cannot start service proxy: driver failed programming external connectivity on endpoint dockerwordpressvip_proxy_1 (8a269964bf883bf2d3e7f4d9ee8a8554a7e91b58f489e739f4e3448657b5d0aa): Error starting userland proxy: Bind for 0.0.0.0:80: unexpected error (Failure EADDRINUSE)
ERROR: Encountered errors while bringing up the project.

This is a wordpress instalation with VIP plugins.
I thought it was a wordpress vip quickstart instalation.

=(

Hey Chris.

New to Phpunit and no Docker expert either. When I run docker-compose exec wordpress tests, it errors out because my bootstrap file is looking for /tmp/wordpress-tests-lib/includes/functions.php.

As per Pippin's Plugins tutorial, I used wp-cli: wp scaffold plugin-tests to create the file structure.

Being that /tmp has a wordpress directory, but no wordpress-tests-lib, I tried running:

docker-compose exec wordpress bash wp-content/plugins/my-plugin/bin/install-wp-tests.sh wordpress_test wordpress 'wordpress' localhost latest

Which errors out without svn installed. I don't imagine installing subversion on the container is the answer.

I'm sure I'm missing a step. Can you point me in the right direction.

Thank you very much for this package set, by the way. I've linked to it from the above tutorial comments as well as from an SO post.

Hey! Is it possible to mount something like

plugins:/var/www/html/wp-content/plugins

Rather than:

plugins/jetpack:/var/www/html/wp-content/plugins/jetpack
plugins/something:/var/www/html/wp-content/plugins/something
plugins/another-plugin:/var/www/html/wp-content/plugins/another-plugin

Object caching is missing from this container, so behaviour may not match the final production environment. The VIP Go MU plugins repo has a memcached dropin already so it just needs setting up in the containers