For initial setup then I am good with the set profile set config add-on apply
But for subsequent restarts, running that same sequence yields lots of messages that look bad to the end-user. So on restarts I am using minishift —profile whatever start The big win on profiles is the ability to start them and stop them often, on the fly, in front of a live audience. Plus, it is best to stop when putting the laptop to sleep to avoid the df cpu problem. Does a subsequent start also get the clock in the VM corrected ? On Sun, Nov 5, 2017 at 9:02 PM Lalatendu Mohanty <[email protected]> wrote: > On Sun, Nov 5, 2017 at 2:09 PM, Burr Sutter <[email protected]> wrote: > >> Trying to use the profiles for an actual demo today - a real production >> use case :-) >> >> one thing I have noticed about the syntax >> >> minishift profile list >> but >> minishift --profile myprofileA stop >> minishift --profile myprofileB start >> >> I need to "list" so I know how to stop/start >> > > This is interesting. So you prefer minishift --profile PROFILE_NAME over > minishift profile set PROFILE_NAME then running config set commands and > finally just "minishift start" command. > > So "--profile" is a global flag which can be used to run a command against > a profile if it is not an active profile. In general we expect the user to > set an active profile and just run the normal minishift commands for that > profile. > > "minishift status" command also tells you which profile you are currently > using. > > >> but one syntax requires no "--" and the other has "--" which I find to >> be odd since I am using the commands back to back. >> >> >> _______________________________________________ >> Devtools mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/devtools >> >> >
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
