These are chat archives for azukiapp/azk
"Automated installation and configuration of development environments" - for pt-BR support, please check out https://gitter.im/azukiapp/azk/pt
Imagine a scenario with three systems: A, B and C, where A depends on B and C is "free".
Then, when I run
azk start A, A and B systems are up. Now, if I enter
azk restart without specifying any system and the
restart would be just an alias for
stop, the system C would be started without being previously started.
We've chosen for an approach where
restart first verifies which systems are up, stop the specified system, and try to return to the same state it was before.
If this is the best approach, I don't really know, but this is the path we chose.
azk restartcommand is, in fact, a little complex and there are trade-offs involved.
[system-name]only acts on running systems, I just assumed it's meant to do
start (all). I think current behaviour (esp when #530 is fixed) is good as it gives flexibility - I can do
stop/startmyself when needed :)