Hosting Meeting Notes: April 15, 2019

Here’s the summary of our meeting in #hosting-community on Wednesday, April 15, 2019 at 1400 UTC (Slack archive).

This was the first meeting at the alternate day/time, and I’m excited to see so many folks!

Attendees: @javiercasares @tylerthomas @j-falk @clorith @boborchard @danfoster @redituk @arvindsingh @katebolin @earnjam @brechtryckaert @mazeheld @tnash @mikeschroder

Hosting Meeting Notes

@redituk noted that he wasn’t able to review meeting notes, so we chatted briefly about the need for folks to review notes/lead meetings and enable that.

@mikeschroder noted that permissions were something we could add, but also that public previews could be enabled if make/hosting had the proper plugin. Since the meeting, this has been added so that anyone can review. Thanks @dd32!

Site Health

As a followup on the chat from last week @mikeschroder suggested folks test the 5.2 beta and linked to a doc that has details on tests and filters for the Site Health tool that is set to ship.

Specifically, he noted that some tests may not apply, or require changes for certain hosts, so please take a look! For instance, there’s a check for automatic update support that requires that WordPress be writable and not have a .git directory. Hosts that have a non-writable WordPress directory or native version control and handle upgrade for users manually may want to change or remove that test using the available filters.

@earnjam pointed out that there will also be a post on make/core soon regarding Site Health.

@j-falk asked if there was any documentation on the PHP modules that Site Health checks for availability. This may be in the upcoming dev note, but in the meantime, it’s visible in the hosting handbook and in the Site Health source.

@mazeheld noted that Site Health was working well for them.

Hosting Automated Testing

@redituk asked to discuss the hosting automated tests.

@earnjam explained that when he set up the tests for Bluehost recently, there were a couple of things he noticed.

First, reporting of the specific error encountered stopped working when the autosave endpoint was merged to core. This makes it so that we can no longer see which tests failed on a host from make/hosting.

Fixing this will involve changes both in the test reporter and on the meta side, but there is currently no way for hosts to know when the test runner/reporter needs to be updated. This makes it difficult to get hosts up to date.

Secondly, some tests were added to core that were failing on hosts that run the tests as root and were since removed temporarily.

He said he’d check to find out which hosts we should contact and recommended we document that the tests should not be run as root (this documentation has since been updated).


If you missed this week’s meeting and have questions or feedback, leave a comment on this post and share your thoughts! OR….Come join for the next meeting!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, April 24th, 2019 at 1700 UTC. Hope to see you then!