Closed alexr8 closed 2 years ago
@alexr8 we are making some changes in 3.0 to either pass the --app
flag or use the current directory.. the list of sites is now gone as most people use nitro is the same directory as the app... We don't specifically have the behavior but we are updating the enable
and disable
commands to start/stop sites (now named apps) from starting with the start
and apply
commands.
@jasonmccallister sounds cool! yeah the main driver was just not having to remember a specific string for a sitename to start a container. looking forward to checking out 3.0 :)
Hi, we are closing this issue as we have decided to retire Nitro, so no additional work will occur on this project. You can read the official blog post here https://craftcms.com/blog/retiring-craft-nitro. We appreciate everyones feedback and involvement and we look forward to refocusing our efforts on Cloud!
If you're looking for a new local development environment, we recommend DDEV and have a knowledge base article to help you with the transition: https://craftcms.com/knowledge-base/migrating-from-craft-nitro-to-ddev.
Description
I'm not sure if this is just me, but i sometimes forget the exact sitename for a given site, and often I just want to run nitro with a single site (e.g.
nitro start mysitename.nitro
). It would be great if there was anitro start this
or similar command that if run from the same directory as the path in the nitro config (where nitro add was first run), it will start the associated container. And the same fornitro stop this
.