You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initially, we built the virtual machine to define a user named
"speaker"
(though in the process of re-branding from "Speaking *nix" to "Command the
Command Line", I'm thinking of changing this to "speaker".). This was to be the
account used by participants in this workshop. I was afraid that the default
"vagrant" user might suggest some non-existent connection between the Vagrant
project and the environment itself. This confusion seems less likely with a
user name that is clearly customized for the course.
...but as I'm troubleshooting some permissions-related issues, I'm having
second thoughts. Given that Vagrant is itself a formal topic for the
course,
it might actually be better for participants to get experience with a more
stock configuration.
Initially, we built the virtual machine to define a user named
"speaker"
(though in the process of re-branding from "Speaking *nix" to "Command the
Command Line", I'm thinking of changing this to "speaker".). This was to be the
account used by participants in this workshop. I was afraid that the default
"vagrant" user might suggest some non-existent connection between the Vagrant
project and the environment itself. This confusion seems less likely with a
user name that is clearly customized for the course.
...but as I'm troubleshooting some permissions-related issues, I'm having
second thoughts. Given that Vagrant is itself a formal topic for the
course,
it might actually be better for participants to get experience with a more
stock configuration.
@tkellen @gnarf @cowboy @MattSurabian @brianloveswords @jennschiffer @reconbot I just
know you will have opinions on this. Mind sharing?
The text was updated successfully, but these errors were encountered: