Skip to content

Conversation

@silverham
Copy link

Allow lando to be used, so we can have multiples of the same project with no conflict and other goodies.

This contains extra ahoy tooling and 'ahoy like' commands via lando tooling a well. A separate PR has been created without lando ahoy like tooling though.

Feel free to adjust code as required. :-)

Joshua Stuart Graham - EY

@tobybellwood
Copy link

I've been working on a slightly simpler implementation over at amazeeio-demos/govcms-lando-demo@main...lando - it relies more on the existing structure rather than a full parallel lando structure.

Where I came unstuck:

  • the lando.type: none implementation in the lando/lagoon plugin doesn't mean don't build it (as the lagoon.type does) - so the services get built locally but without any kind of configuration equivelent in lagoon/lando
  • Lando v4 is just around the corner, and will be turning a lot of the processes on their heads, so we're keeping a watching brief on that
  • there may have been something else, but it slips my mind for now!

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

Successfully merging this pull request may close these issues.

3 participants