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

Cloudways (interface for DigitalOcean, AWS, Linode)

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.

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

Added child issue for UK host Mythic Beasts.

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.

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 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? I have updated the #3455589: Test Project Browser on Hetzner 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 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 on the Hetzner page (#3455589: Test Project Browser on Hetzner) (and deleted the original "Proposed resolution" list) but perhaps the wording could be improved?

Remaining tasks

Go through the "Steps to include in the child issues" in the [META] Test Project Browser on hosting providers 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!

For comparison, see #3453718: Test Project Browser on Dreamhost which still has the to-be-removed list:

Proposed resolution

1. Write Drupal install notes above
2. Go through Drupal install
3. Enable and test Project Browser
4. Make sure to actually install a few modules
5. Note any extra steps to make it work
6. Note any problems
7. Make follow up issues as needed

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, 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?

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 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.

I recently had some fun getting automatic updates to work on Hostinger (playing around doing a hobby site) and ran into some generic problems that might help with other hosting platforms. Here are the issues I opened:

• #3511959: The message displayed when proc_open is not available could be better - with Drupal CMS the error is not obvious because automatic updates currently ships with an old package_manager
• #3511967: Package Manager tasks can exceed wait_timeout on cheap hosting - database timeouts will present as an exception while installing a module via project browser
• #3511972: Allow Composer and rsync location to be configured via the UI - I think we could provide a bit more help and UI to configure custom composer locations