Open tomjn opened 4 years ago
@tomjn As someone who has started using VVV today and has this same article open in another tab, can you provide any pointers as to what is outdated and what needs changing?
The most striking one is that it refers to vvv.dev
, use vvv.test
instead. We also got rid of the wordpress-default
site in favour of wordpress-one
/wordpress-two
/etc
It also uses /vagrant/www
, which only worked in the past by accident, it should have used /srv/www
and as of VVV 3.x the old folder own't work
You'll also want to swap mentions of local.wordpress.dev with a URL for a newer site.
Aside from those parts, the article is mostly accurate and things work pretty much the same
We actually have a WIP doc of our own for doing this that works, someone donated it from their internal company documentation :) It's not merged yet as I want to make stylistic changes, but we've had someone follow it and test it out with success:
https://github.com/Varying-Vagrant-Vagrants/varyingvagrantvagrants.org/pull/174
Look here for the rendered preview:
If you can share any thoughts on it I'd really appreciate all feedback you have!
GitHub
I asked Gary who wrote the post, he doesn't work at Jetbrains anymore, and the official account replied saying they don't edit old posts but rather post new ones with updated info:
https://twitter.com/phpstorm/status/1265987394261696512
I need to put together something and sort out a new post
“@Tarendai Hi! We don't usually edit old blog posts but rather publish updated versions. You can forward us your notes via Help | Contact Support or Help | Submit Feedback.”
There's a blog post over on the PHPStorm blog that's a little old:
https://blog.jetbrains.com/phpstorm/2016/06/debugging-vvv-vagrant-setup-with-phpstorm/
Some adjustments would improve it by bringing it in line with modern VVV, we should reach out to JetBrains/Gary and offer help