Using Lando with multiple projects and team members

[axroth]

Hi,

I'm currently evaluating lando against the toolset I have been using in our agency so far. While lando itself seems to be a great tool in a single project context, i'm still searching tools that help to have a consistent toolset across all projects locally installed. Perhaps someone can answer these questions or give hints to addons/plugins that exist and are not part of lando core.

• how can i update lando itself to the latest version (is there an automation for this?)
• how to (automatically) distribute a custom plugin /recipe between team members?
• is there a script to rebuild all lando installed projects, even if not running/active?

Are there some other best practices for teams you would recommend?

Best, Axel

[pinoniq]

We commit the .lando.yml file to the repo. Works like a charm. just git pull && lando start For distribution of custom plugin/recipe -> just use the existing toolchain. e.g. git

And conerning ur 3rd point, not sure why would want to do that imho

[axroth]

We commit the .lando.yml file to the repo. Works like a charm. just git pull && lando start

for sure, that's what we do as well. :)

For distribution of custom plugin/recipe -> just use the existing toolchain. e.g. git

so you would distribute/update custom plugin/recipes to the user's home directories using git + cron?

And conerning ur 3rd point, not sure why would want to do that imho

if a (shared, custom) recipe has changed, all my instances should be rebuild to have a consistent state. Imagine 100 projects and 10 developers...that's a lot if different states if not managed somehow.

[axroth]

Perhaps this helps someone. So, what we do now is:

• we have a custom composer plugin that runs on composer install/update
• it installs/updates, githooks and some more things we want to have consistent across projects
• there is a githook that identifies if there were changes in one of the lando-files, if yes, it shows the differences
• developer can then choose to rebuild or ignore
• we are using a .lando.base.yml to have a solid, shared base of all projects, and a .lando.yml that adds or overrides some things in project context. the .lando.base.yml is also shared with the mentioned composer plugin
• the base contains things like tooling, xdebug setup, additional services, events and git-configuration

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions and please check out this if you are wondering why we auto close issues.