Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement SimplyTest.Me functionality on Lagoon #191

Closed
4 tasks
Schnitzel opened this issue Jan 15, 2018 · 11 comments
Closed
4 tasks

Implement SimplyTest.Me functionality on Lagoon #191

Schnitzel opened this issue Jan 15, 2018 · 11 comments

Comments

@Schnitzel
Copy link
Contributor

Schnitzel commented Jan 15, 2018

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?

@geek-merlin
Copy link

+10 from me for moving to docker architecture.
Plan seems reasonable!

@jonathanjfshaw
Copy link

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.

@jonathanjfshaw
Copy link

There are very interesting caching possibilities with Docker, such as having an installed D8 core sitting in the Docker cache, so spinning up is very fast, just needs to install any desired modules.

@Schnitzel
Copy link
Contributor Author

@axel-rutz thanks!
@jonathanjfshaw
oh wow, that sounds even cooler! That would actually definitely be possible to directly edit code directly in a cloud9 container or so.
Also, yes full agree, Lagoon actually shares Docker image caches among multiple projects, so a Drupal installation would be cached :)

@forethoughtde
Copy link

Sounds interesting. I would like to help out.

@theodorosploumis
Copy link

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

@Schnitzel
Copy link
Contributor Author

Schnitzel commented Jan 25, 2018

As mentioned by Dries over here: https://twitter.com/Dries/status/956481436512595968

The current plan tries to keep the current SimplyTest.me Frontend UI and thinks about implementing the underlying architecture.
BUT: If some people are interested in coming up with a new UX and UI for the User Facing Simplytest.me, that would obviously also be awesome :))

@thom8
Copy link
Contributor

thom8 commented Jan 25, 2018

@Schnitzel put together a very simple project utilising composer + docker + helm (k8s) -- https://github.com/thom8/simplytest

Currently, have a PoC running on GKE /w preemptible VMs to lower costs, there's no cost for the control plane, nodes can be automatically updated and set to autoscale.

Also configured to cache composer dependencies so a new instance can be spun up in ~10s., but some layer caching here could make that even faster.

Working on some docs for running the helm chart on a local cluster for easier testing.

@forethoughtde
Copy link

I am interested in coming up with new UX and UI for the user facing Simplytest.me. Even though, the current interface does the job we can better it. Any thoughts?

@jonathanjfshaw
Copy link

jonathanjfshaw commented Jan 25, 2018 via email

@dasrecht
Copy link
Contributor

dasrecht commented May 4, 2019

Closing this due to inactivity and due to the fact that the project has a path forward with a new maintainer.

Update: Patrick has handed over the maintainer-ship of Simplytest.me to Adam Bergstein. With this the immediate future of Simplytest.me is secured! Thank you, Adam! ❤️

via https://stories.amazee.io/save-simplytest-me-e564c13e9fb8

@dasrecht dasrecht closed this as completed May 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants