Test Project Browser on Cloudways

Cloudways is a managed hosting provider with an easy to use interface for various cloud services. They are owned by DigitalOcean, but also provide servers at Vultr, Linode, AWS and Google Cloud. Each server is billed for usage after a three-day free trial period.

Drupal install notes
Login to your Cloudways account and select an Application of type PHP Custom.
Enable SSH on the server or application and login using a terminal
Make your way to the application public_html and paste in
composer create-project drupal/recommended-project starshot

Go through Drupal install
In the Cloudways Application settings, change the web root to /starshot/web/
Browse to your new site and complete the Drupal install
Copy and paste the database credentials from Cloudways
Enter your site name and admin credentials

Enable and test Project Browser
In SSH terminal
composer require 'drupal/project_browser:^1.0@beta'
In your browser, navigate to Extend, and tick Project Browser and Project Browser Source Example and click Install
Return to Extend and select the Browse tab
Select Drupal.org (mocked) and use Search for modules to find a specific module (Pathauto) and click on Install.
The module is added, and the interface displays the list at the Pathauto entry
Click to enable
Filter by Category to find other modules needed (Webform) and click on View Commands to copy the composer string required to install by SSH.

Note any extra steps to make it work

Note any problems
I was unable to configure "Allow installing via UI (experimental)" due to it's requirement for Automatic_updates. When I attempted to install that module I got:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/automatic_updates[3.1.0, ..., 3.1.2] require php-tuf/composer-stager ^2-rc2 -> found php-tuf/composer-stager[dev-develop, v2.0.0-rc2, v2.0.0-rc3, 2.x-dev (alias of dev-develop)] but it does not match your minimum-stability.
    - Root composer.json requires drupal/automatic_updates ^3.1 -> satisfiable by drupal/automatic_updates[3.1.0, 3.1.1, 3.1.2].
    Make follow up issues as needed

Thanks @kathc for a very thorough and detailed description!

I was skimming all issues, to see if any hosts had been tested yet, and only saw your great work by chance, when I wanted to edit the issue summary, and add the "Make sure to actually install a few modules" step.

I have taken the liberty of moving it into the Issue Summary, and changing Status to "Fixed", since you have verified that Project Browser works on Cloudways. This way, the Cloudways issue will visibly be marked as "Fixed" in the list on 📌 [META] Test Project Browser on hosting providers Drupal people are using Active .

I assume that "Allow installing via UI (experimental)" is not yet expected to work? But if it is, feel free to change Status to "Needs work".

Fantastic work 🎉 thanks to you both 👍

You're welcome @Kristen Pol, thanks for all the great work you are doing with Project Browser!

Since it looks like this issue is fixed, will you be setting credits, or perhaps someone else will? I ask because during the last year, automatic crediting in issues has been disabled, to avoid cheating ... I am not sure this was such a great idea, because now maintainers need to actively set them, after an issue reaches the "Fixed" status ... and credit is sometimes not set.

For more about crediting, see #3395901-27: Use Gitlab CI in Simplenews → . (though, you likely are already aware of this ...)

I’d be happy to assign credit but I’m not a comaintainer. I can ask about that.

Thanks! It would be great to get it cleared up.

Re-opening. The point of these is primarily to test it WITH the experimental UI on. That is what will require a lot of work and figuring out if permissions are allowed, etc.

We need someone to be able to turn the module on, turn on Package Manager, and then check the "Allow install" checkbox, and then go to Project Browser and click "Add and Install" with a module, and make the hosting work if possible with that solution.

That's the real work here.

Thanks for the clarification Chris. I will try to get it working tomorrow.

I created a page for Cloudways → .

Ressa, are you doing the same testing and writing more documentation about using Cloudways? I don't want to duplicate the effort if so.
I am not connected to Cloudways, I just use it for some of my hosting needs so it's the most likely place I'll want to use in future.

Sorry @kathc! I was busy yesterday, so I just quickly created the Setting up Project Browser on your hosting provider → (a "Guide") and a few sub pages (Cloudways, Dreamhost, and Hetzner) and didn't clarify what the new Cloudways page was for.

I had hoped for feedback from @chrisfromredfin about this new Guide, as well as some other questions in the META issue 📌 [META] Test Project Browser on hosting providers Drupal people are using Active , after I created the Guide yesterday ...

But yes, please add the steps in the Cloudways → doc page.

And by the way, the steps in the META issue have been updated to this (the steps under "Proposed resolution > 1. Write Drupal install notes above" on this page):

Steps to include in the child issues:

1. Attempt to install a few modules
2. Note any extra steps to make it work
3. Note any problems
4. Make follow up issues as needed
5. Create a "Page" under Setting up Project Browser on your hosting provider → , with the instructions needed to make the setup work for that provider

From [META] Test Project Browser on hosting providers 📌 [META] Test Project Browser on hosting providers Drupal people are using Active .

PS. @cbrovard asked the same question in 📌 Test Project Browser on Dreamhost Active , so this answer is virtually identical. It just goes to show, that a little extra text is often useful, to keep issues like this moving :)

Thanks @ressa for moving the documentation forward! 😍

You're welcome @Kristen Pol! And thank you for your great efforts here, as well with the +100 logo issues you just created. It's a really great feeling of a team effort, with issues constantly evolving all around.

Adding link in Issue Summary.

Update Issue Summary "Remaining tasks", linking to parent issue.