Implement SimplyTest.Me functionality on Lagoon

Background:

• Maintainer of Simplytest.me searches a future for Simplytest.me https://www.drupal.org/project/simplytest/issues/2932684
• We think Lagoon is the perfect base for such a tool, why:
  • It allows fast spin up and spin down of individual environments
  • Each environment is completely separate of each other, no risk of one environment killing or accessing the other one
  • Each environment can be completely different (different drupal, different php, etc.)

Overall Architecture: Important: This is generated by @schnitzel without a huge background of knowledge about simplytest.me itself. So this might need to change.

1. Current Simplytest.me interface is reused, User clicks on “launch sandbox”
2. Simplytest Frontend talks to Lagoon API and creates a new environment for a Project
3. Simplytest somehow (tbd) tells Lagoon what the user has selected (which Drupal, which Modules, which patches, etc.)
4. Lagoon creates new environment and starts a Build (probably not the current OpenshiftBuildDeploy but another new one that is created with this project)
5. Build starts and Builds a Docker Image with the defined Core, Modules, etc. (here we might can reuse some of the already existing simplytest scripts)
6. Simplytest UI checks with Lagoon API if environment is deployed and if successful redirects the User to the generated URL

Next Steps:

• Validate Architecture
• Create individual tasks for work based on Architecture
• Find people that want to help
• Get work done

@everybody What do you think?

[theodorosploumis]

I have created https://www.distros.bid/ (using Docker) to personal replace Simplytest.me some month ago.

[jonathanjfshaw]

Very excited to hear about this. It’s a small step towards one day having a cloud IDE for drupal, would make it so much easier to test and tweak patches, increasing d.o. issue queue velocity.