Skip to content

Instantly share code, notes, and snippets.

@smith

smith/lc-notes.md

Created June 30, 2014 22:33
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save smith/ec51b4cdd4c214b455f3 to your computer and use it in GitHub Desktop.
Save smith/ec51b4cdd4c214b455f3 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
lc-notes.md
  1. get a vm 4:11 - 4:14
  2. configure a resource 4:14 - 4:23
  • Running the terminal in a different window is weird, especially since it's a browser window and not my terminal and I have to keep context-switching in between the two.
  • It tells me to create a file and edit its contents and save it, which assumes that I know how to do all of these things from a unix shell or a linux desktop. If you're running in the console you can do gedit hello.rb & which gives a nice editor. Maybe we should make this the default.
  • It says, "From your terminal window, run chef-apply to apply what you've written.", but below it says to run "chef-apply hello.rb". If you just run chef-apply, you get "TypeError: no implicit conversion of nil into String", which isn't very friendly. The commands should match and the error output should say something that makes sense.
  1. configure a package and a service 4:24 - 4:30
  • Maybe the desktop should just have the icons for the things we're using on it
  1. Make your recipe more manageable 4:40 - 4:48
  • "Create a cookbook file" is not actually creating a cookbook_file, but a template. Maybe we should call it a template up front to avoid confusion later (they probably don't need to know what a cookbook_file is at this point anyway.
  • It's annoying that in all our docs we call it a "run-list" but chef-client makes you use "--runlist" and doesn't support "--run-list".
  1. Get ready to add another server 4:49 - 4:57
  • The version of firefox on the vm gives a modal on manage about the browser being to old, but it seems to work fine after you dismiss that.
  • It tells me to log in to hosted chef and go to Administration, but doesn't tell me about the creating an org part. Once I create a new account and create an org, I'm dropped on the page with a big button to download the starter kit, so I don't need to go through the steps in learn-chef. Maybe learn-chef should tell me to click the big button once I'm in, and tell me to go to https://manage.opscode.com/starter-kit if I already have an account.
  1. bootstrap a node 4:59 - 5:11
  • Clicking the button to open the new cloudshare env takes me away from my console session in the earlier env. Not sure how to get around this.
  • The clipboard interaction in cloudshare is kind of a bitch. Wasn't immediately obvious on how to use the "Send Text..." to copy/paste
  • If you're bootstrapping with root I don't think you need --sudo
  • Is there any reason to use --bootstrap-version? I've never needed to use it. Is this because chefdk is running a weird version or something?
  1. dynamic config 5:13 5:24
  • oh my god typing in the console mode is so slow kill me
  • the ending should have some links on what to do next: stuff to read, go to management console, community cookbooks, etc. I wonder what existing content would be the logical next step at this point?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment