-
Notifications
You must be signed in to change notification settings - Fork 0
Stop 'local' containers when starting 'dev' containers and vice versa #27
Comments
I also keep making that mistake 😅
Yes, we should do that.
I think that a better approach would be to run |
local
and dev
containers at the same time
I had started poking at the "stop local containers when starting dev containers, and vice versa" aspect of this in kdmccormick/tutor#3, but, as Régis and I had talked about, it'd be way easier to just implement this on top of the V1 Plugins branch. |
Blocked by #32 |
Will be Resolved by overhangio/tutor#646 |
Context
tutor local ...
commands start one set of containers.tutor dev ...
starts a different set. If someone tries to run both at the same time, they will find that one's ports conflict with the other's.Because there is no
tutor dev quickstart
command, first time developers always need to:tutor local quickstart
, thentutor local stop
, andtutor tutor dev start
.The Tutor dev docs do call this out:
but I worry that this will be an easily overlooked stumbling block for new users. I certainly messed this up the first time :P
Do we think that others would find this confusing too? Could we remove/mitigate this stumbling block by:
tutor dev quickstart
that spins up dev-mode containers, orlocal
/dev
containers while the other set is already up?Acceptance
Referencing @regisb's comment below:
tutor dev stop
as part oftutor local start
, and to runtutor local stop
as part oftutor dev start
.Introducetutor dev quickstart
, analogous totutor local quickstart
. Update the docs.The text was updated successfully, but these errors were encountered: