WordPress.org

Making WordPress.org

Opened 3 months ago

Closed 3 months ago

Last modified 3 months ago

#5879 closed defect (fixed)

[Core Handbook] Invalid Plugin Vagrant Hosts Updater

Reported by: AMYunus Owned by:
Milestone: Priority: normal
Component: Handbooks Keywords:
Cc:

Description

I followed tutorial installing VVV on the Core Handbook and found error while doing step 3 Installing Vagrant Hosts Updater. After following the link to Github repo of the plugin, it said that the plugin is no longer maintained and suggesting to use other alternative.

First, the page of the handbook last update is April 9, 2020 (more than a year ago) and the plugin is no longer maintained since March 3, 2021.

Second, I'm not sure if the section could be removed or should be replaced with something similar or relevant.

Attachments (2)

Screen Shot 2021-08-27 at 05.13.39.png (161.2 KB) - added by AMYunus 3 months ago.
Error after doing command vagrant plugin install vagrant-hostsupdater
Screen Shot 2021-08-27 at 04.38.00.png (1.3 MB) - added by AMYunus 3 months ago.
Plugin maintainer said it is no longer maintained and suggest to see other alternatives

Download all attachments as: .zip

Change History (9)

@AMYunus
3 months ago

Error after doing command vagrant plugin install vagrant-hostsupdater

@AMYunus
3 months ago

Plugin maintainer said it is no longer maintained and suggest to see other alternatives

This ticket was mentioned in Slack in #core-docs by dd32. View the logs.


3 months ago

#2 follow-up: @netweb
3 months ago

You can try this:

Some operating systems have issues with Avahi so the Chassis host names don't automatically resolve. As a workaround you can install the Vagrant Goodhosts plugin by running vagrant plugin install vagrant-goodhosts and then add the following to one of your configuration files:

hostsupdater: yes

I've not tested this myself, and it comes from a similar issue I recalled with Chassis:

#3 in reply to: ↑ 2 @AMYunus
3 months ago

Replying to netweb:
Thank you for the reply and the solution offered. I am going to try it and report them ASAP here.

My intention by reporting them here is to avoid other same questions from other future newly contributors (like me). Do we need to still promoting the plugin (that is no longer maintained) in the handbook?

I think we have 3 options here :

  1. Remove the step (only if the step is not mandatory to follow)
  2. Replace the step with something manual config
  3. Add troubleshooting step as you mentioned in the handbook

What do you think?

#4 @TJNowell
3 months ago

@AMYunus VVV does not recommend vagrant-hostsupdater, we actually recommend vagrant-goodhosts not hostsupdater precisely for the reasons you've outlined.

The problem here is that .org duplicated our install instructions then didn't keep it up to date. I have eliminated the problematic step as it is already covered by the VVV documentation.

#5 @TJNowell
3 months ago

Now that this is done, this can be closed. For reference, you can install the relevant plugins with this command:

vagrant plugin install --local

#6 @netweb
3 months ago

  • Resolution set to fixed
  • Status changed from new to closed

Thanks for the follow up @AMYunus and handbook update @TJNowell

I'll close this ticket now.

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


3 months ago

Note: See TracTickets for help on using tickets.