heygrady / docker-wordpress-starterkit Goto Github PK

@heygrady You probably already know this but it's worth filing a todo on it. This line references the container tldr_db_1 directly, so when the name tldr isn't used then this reference is empty:

$(docker ps --format \"{{.ID}}\" --filter \"name=tldr_db_1\")

Docker thinks you're looking for a container named 'mysqldump' at that point, so it errors out. Like I said, sure this is just a todo or feature request. I can expand on that if needed, but basically we should eventually be able to set a specific project name (slug or domain of the site) and use that to run these commands.

@heygrady thanks so much for this awesome kit!

I ran into an issue on the first install of this using your most recent TLDR; instructions. when running them exactly as stated, the script was throwing an error on the npm run docker:up:daemon command:

$ npm run docker:up:daemon

[email protected] docker:up:daemon /Users/xxxxxx/tldr
npm run docker:up -- -d


[email protected] docker:up /Users/xxxxxx/tldr
npm run docker:pf -s && docker-compose up "-d"

Creating volume "tldr_data" with default driver
Creating tldr_db_1
Creating tldr_wordpress_1
ERROR: Container command '/entrypoint.sh' could not be invoked.

I found a few issues related to this on other projects, they suggested that the problem was that after copying entrypoint.sh, it needs to be set as an executable. The fix I added as part of this pull request #1

One thing that is extremely confusing to me is that even when I fixed this, stopped all the containers and even restarted the default docker machine, I got the same error, even on a clean repo of this project. I was able to fix by completely deleting the default docker machine and starting from there.

Seems like the incorrect permissions persisted across boots. Would re-provisioning fix this?

Both style changes and PHP file changes sometimes don't show up immediately. Would be nice to have an option to turn caching on or off, since we usually want it off while developing.

When loading up stanthony's through Docker I got this error: Fatal error: Uncaught Error: Class 'ZipArchive' not found.

Adding this line: && docker-php-ext-install gd mysqli opcache zip fixed the Fatal error. This is line 12 in the Dockerfile.

Error response from daemon: No such container: mysqldump is the error I'm getting on Blue Matter Consulting, a local dev set up I just created on the 11th (July 11, 2016). The dump gets this far:
rolling schema adding: 01-schema.sql (stored 0%) dumping schema
and then errors out.

I have not checked dependencies for grunt versions yet. I will do this and respond to this ticket.

Looking into this a bit, will submit pull request soon-ish...

This is something i'm working on now. With this, we'll be able to start using it in place of Vagrant immediately.

Also gonna work on documentation a bit more.

I dont know why im getting this error...
npm is working fine on my end...

i successfully do npm install...
then have my docker toolbox working...
but when i try to run
npm run bedrock:init
it throw me these errors

> [email protected] bedrock:init C:\Users\Uriah\Docker\wordpress.dev
> git clone $npm_package_config_repo bedrock && cp .env.example bedrock/.env

fatal: repository '$npm_package_config_repo' does not exist

npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "bedrock:init"
npm ERR! node v5.10.1
npm ERR! npm  v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! [email protected] bedrock:init: `git clone $npm_package_config_repo bedrock && cp .env.example bedrock/.env`
npm ERR! Exit status 128
npm ERR!
npm ERR! Failed at the [email protected] bedrock:init script 'git clone $npm_package_config_repo bedrock && cp .env.example bedrock/.env'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the docker-wordpress-starterkit package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     git clone $npm_package_config_repo bedrock && cp .env.example bedrock/.env
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs docker-wordpress-starterkit
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls docker-wordpress-starterkit
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Uriah\Docker\wordpress.dev\npm-debug.log

The read me should be reduced to reference the starter kit itself. The current file should be broken up into a docs folder where more robust docs can live, like the write up of how this repo got started or recipes for common setups or instructions for cloud deployments ;)

We already kind of knew about this but there should be something in the docs (which I can add in) or, even better, some sort of terminal output during docker:up encouraging the user to be patient as the site comes up at http://localhost:8080. In every instance, when I run that command, it takes Apache or PHP or maybe MariaDB at least a full minute to get going, and until that point port 8080 throws no response.

It'd be great to come up with a graceful solution here, but I think first I want to figure out what's taking so long. Maybe @heygrady already knows, without any other information I'm suspecting Apache is doing something weird since we're not getting even an error page during this dead-zone.

Working on parsing this, will throw it in the docs when I get a good howto

We usually use gulp watch which opens up localhost:3000 for hot reloading, but this doesn't work. Any way to get this to work?