-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Duplicate project name detection and prevention #80
Comments
A quick update on this, as @gitressa pointed out in my other Issue, seems like this is caused because I had the same app name for both the WordPress and Laravel app. Maybe the app tried to cache it somehow and kept conflicting, but naming things correctly fixes the issue. Sorry, my bad. |
Thanks for creating this issue @MatheusMK3. It is important to not have identical names for different The easiest and most efficient way of starting all over with fresh Lando instances, should you ever need it again, is this method: https://docs.lando.dev/help/purging-containers.html @labboy0276: Is it somehow possible to block the creation of a Lando instance, if the name already exists? Perhaps something like this?
... as well as:
|
@gitressa I will rename this issue and make it a feature request. We are all heads down on Lando 4 stuffs now, so I don't think it will be considered for quite sometime. |
@labboy0276 I am looking forward to Lando 4, and agree that you should totally focus on getting that done first. |
Glad to see this might come as an improvement! Looking forward to it! |
Lando v3.6.5 here, but also happens on v3.6.4
Basically, the main issue here is that if you have two projects/directories with different recipes/plugins being used, Lando will not pick up the recipe/plugin specified in the current Landofile and not only will show you invalid commands if you run
lando --help
, but also will completely ignore any commands valid for the active Landofile.Reproduction:
lando-A
andlando-B
lando-A
lando --help
and take note of the options,lando artisan
andlando laravel
should be presentlando-B
lando --help
and take note of the options,lando wp
should be presentThe only thing I found that fixes this situation is going to the project directory and running
lando start
orlando rebuild
. It seems to update some sort of cache and becomes the "current" Lando application.A bit related, but something I noticed is that it's possible to run Lando commands such as
lando laravel
before starting or rebuilding the project for the first time. This leads to a bit of confusion because it will start the containers just as one would expect, but not download any CLI binaries, which will lead to an error saying the binary was not found.Hope the report is somehow helpful, I've been using Lando for about a month now and it's a quite useful tool! Just found those small details to be a bit confusing or unexpected...
The text was updated successfully, but these errors were encountered: