search

ideasonpurpose / basic-wordpress-vagrant

A fast, easy to use WordPress Vagrant environment modeled after managed WordPress hosting platforms like WP Engine and Flywheel.
MIT License
25 stars 3 forks source link

No such file or directory .ip_address #68

Closed entozoon closed 5 years ago

entozoon commented 5 years ago

Vagrantfile:66 is complaining this file doesn't exist.

Do I create that file myself? Possibly containing the intended IP for the machine?

entozoon commented 5 years ago

Hmm, actually I can't replicate it. Must have had a borked VBox VM instance, my apologies!

joemaller commented 5 years ago

Actually I just saw something similar on another vagrant project and this helped me figure out a better solution over there.

That /vagrant/.ip_address file was a bit of a hack and way too fragile. The file got written as a side-effect deep in the wp_config task here: https://github.com/ideasonpurpose/basic-wordpress-vagrant/blob/8409cc67ac8128110f7b75fb20dafecc5e610084/ansible/roles/wordpress/tasks/wp-config.yml#L3-L5

It would be nice to store the IP address in a variable in the VagrantFile, but I couldn't figure out how to hook the Vagrant:Machine instance outside of the plugin block. So instead, I added a one-line shell provisioner which explicitly writes the .ip_address file.

It's a lot better over here: https://github.com/ideasonpurpose/basic-wordpress-vagrant/blob/ba0af714a6e1be86e52a164e9501dc4dead4a2e6/Vagrantfile#L107-L109

I've also been having issues with Apache failing to restart, so I added a one-liner to force-kick that too.

Thanks for reporting, even if it was just a glitch 👍

entozoon commented 5 years ago

Fair enough, great work dude!