wordpress-dev | A library containing my standard development resources | Awesome List library

You need to mount the image file to the nginx container, because static content is served via the nginx container. The Php container only executes the php.

I did it by adding on the parent

After digging through the internet a little bit, I was able to read through some more documentation as well as some other examples and I was able to figure out what I was doing wrong. Overall, I was close, but I ended up cleaning it up and just using the WordPress get_theme_mod() outright in my template file (in this case it was the footer.php file).

Here's what I ended up with:

I've used Varying Vagrant Vagrants, which is great for WordPress development for a pretty long time, recently I've switched to Laravel's Homestead, which is also great and works fine with WordPress too.

Both are pre-made environments that are easy to install, pre-configured and ready to use. Never had any issues with them.

You could use composer's post-update-cmd or post-install-cmd option. This is executed after a composer update/install. Add this to composer.json:

After much digging, I found the answer.

@Devon was correct in that I should add the WordPress files (i.e., download them from the WP site, unzip them, and add them) to the subdirectory wwwroot.

The next error was Error establishing database connection, and apparently there is a problem with the version of mysql that I had been using. I had been using MySQL Community Server 8.0.11. But according to this post from an unrelated project, v8.0.11 of mysql has issues with php 7.1.

I completely uninstalled/deleted mysql v8.0.11 and then did brew install mysql@5.7.

After installing v5.7, I logged in to mysql (as root user), and just ran:

Anything defined in require-dev is always what you need to provide new functionality in the current library.

Then if you depend, on another library, this library need only to correctly working what is in require, but without require-dev.

Then login with this, you don't need part of require-dev from dependent libraries, for your own development. The flag itself update --dev will load everything.

With scenario:

Also in the composer.json of vagrantin/wp-nonce, if I'm setting cyruscollier/wordpress-develop in require-dev instead of require. I'm downloading only "wp-nonce" either with composer update or composer update --dev.

I think everything is correct.

With the second scenario, where you mark vagrantin/wp-nonce as require-dev, and in inside vagrantin/wp-nonce you cyruscollier/wordpress-develop as require - then, in my opinion, this should resolve in download both, with standard calling composer update.

Call additional steps

• check update on packagist if your repositories are correctly loaded or other services you use.
• run composer self-update

I think this all should clear the problem.

What happens when you run env mysqldump command in shell? You can install and use strace for example and run the script or just the failing command like strace -F . Maybe you will reveal more details about this error.

The problem was that the Wordpress cartridge had Wordpress version 3.9. Updated Wordpress to the latest version (4.8) and everything worked also locally.