[META] Test Project Browser on hosting providers Drupal people are using

Capitalize name :)

Start filling in a list.

Thanks :) Adding more hosting providers. Open to more in the list!

I will add the child issues once we've added a few more providers to the list.

Cloudways (interface for DigitalOcean, AWS, Linode)

Thanks!

Adding more child issues.

Alphabetize list and link to remaining child issues.

I have a Drupal site on Hostinger. I will test Project Browser there. I can open a new child issue and assign it to myself, if that's the preferred flow?

We definitely want to test on Hostinger, if no one has done so already, because they are listed on the Drupal.org/hosting page.

Thanks 🙏 yes, please add a child issue by cloning one I created as it has some structure and then changing the provider name in two places and then update the issue summary here to include it alphabetically in the list and link it to the child issue… makes it easier to see which providers.

One of my previous go-to cheap hosts for Drupal was ICDSoft.

Added child issue for UK host Mythic Beasts.

Thanks! Updated summary to provide instructions for adding new child issues and updating the list.

Fix typo and more clarification in summary.

Clean up instructions.

Added bullets that should be included on child issues.

Add "how to contribute" section.

Minor formatting changes.

Minor formatting changes.

Add Hetzner, and extra step in the "Please add a child issue by", to update parent issue in the cloned issue.

Alphabetize the list -- also, switch to using reference links for easier alphabetization, and more easily see the status of individual issues ("Active", "Needs review", "Fixed", etc.).

Feel free to revert the list to manual links, if you prefer that :) I just thought I'd be bold and do the change, to try it out.

Fix Hetzner issue link.

Thanks 🙏

We could house all the hosting providers as pages under a "Hosting Providers" Guide, so I created Setting up Project Browser on your hosting provider → .

Perhaps someone can add it to the menu, and edit the title and description if necessary?

I added an example page of a hosting provider (Hetzner).

I also added creating the handbook page as the final step in the Issue Summary, in this issue summary.

To simplify things, we could delete the list of tasks from the individual child pages, and refer to this META page instead, to simplify things? I have updated the 📌 Test Project Browser on Hetzner Active issue as an example:

Remaining tasks

Go through the "Steps to include in the child issues" in the [META] Test Project Browser on hosting providers 📌 [META] Test Project Browser on hosting providers Drupal people are using Active issue.

The wording can surely be improved, feel free to edit and improve it ... If and when we agree on a good wording, I can update the child pages.

With this structure, we are free to refine the steps under "Steps to include in the child issues" without having to update +20 issues :)

I created doc pages for Cloudways → and Dreamhost → , since they are in progress.

@Kristen Pol and @chrisfromredfin, what do you think about my suggestion in #35?

It would be super awesome to agree on the wording, before updating all the hosting provider child issues.

@ressa - first of all, love the stubs in the Handbook, that's exactly what I had in mind.

I totally agree that you want to refer to base instructions in the meta, so that if we ever want to update them we just have to update them in one place.

What is the specific language/wording you want me to look at? I am having trouble digesting what specifically you need feedback on! Thanks for your efforts, this will be amazing. :)

Sounds good @chrisfromredfin, I'm glad I could help out with that.

And about the wording ... Sorry if it wasn't clear, but it's how to formulate the sentence on each provider page -- the sentence which refers back and links to this issue, for the actual list of steps to complete for each provider.

So I have made a single example of the wording on the Hetzner page ( 📌 Test Project Browser on Hetzner Active ) but perhaps it could be improved?

Remaining tasks

Go through the "Steps to include in the child issues" in the [META] Test Project Browser on hosting providers 📌 [META] Test Project Browser on hosting providers Drupal people are using Active issue.

That's the sentence I wanted to run by you all, before going ahead with updating all providers, deleting the list, and replacing it with this. Thanks!

PS. Perhaps you can add the new Guide https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... → to the menu (you can see it says "This guide has not yet been [...] added to the menu."), and edit the title and description if necessary?

Or perhaps add it me as maintainer of https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... → ?

Thanks @ressa for moving the documentation → forward! 😍

Thanks, this looks helpful!

A couple questions for clarification:

Many of these hosting providers offer multiple types of hosting, such as dedicated hosting, cloud hosting, VPS hosting, and shared hosting. Is the plan to test all types of hosting or are there minimum requirements?

Are you looking for people to start testing now or wait for further instructions/developments?

I was suggest testing whatever people are comfortable testing. I’d rather start testing something for each provider than wait for someone to have time to test all services.

Thank you Kristen Pol! And by the way, do you think this is good, or needs tweaking before I update the issues, as I described in #40?

Remaining tasks

Go through the "Steps to include in the child issues" in the [META] Test Project Browser on hosting providers 📌 [META] Test Project Browser on hosting providers Drupal people are using Active issue.

@camhoward: I agree with Kristen Pol, please test the type of hosting you're most comfortable with.

Updating sub header to "Steps to include for each hosting provider" (was "Steps to include in the child issues").

All hosting provider issues are now updated.

Thanks 🙏