Skip to content

Instantly share code, notes, and snippets.

Ryan Cromwell cromwellryan

View GitHub Profile
@cromwellryan
cromwellryan / TALKS.md
Last active Mar 8, 2017
Dayton Clean Coders 2017-03-08 Lightning Talks
View TALKS.md
View README.md

Agenda:

  • Cromwell: Opening
    • [Gem City JS] Wed, Nov 19: Home Automation and Robots using Johnny-Five with Rob Tarr
    • [Dayton Web Developers] Wed, Nov 2: Brian Woodward - Going 'serverless' with JavaScript, APIs and Markup (JAM)
    • [Southwest Ohio Givecamp] Fri, Oct 21: 141 Volunteers THANK YOU!!!
  • Introduction to [Hacktoberfest]
    • What does it mean to contribute while at DCC?
    • [Progress Checker] Examples: [cromwellryan progress], [tarr progress]
    • Share your progress at [Dayton Web Dev Slack]
  • [Sign up]
View README.md
  • Install Docker Platform for Mac
  • Cronjob to remove Dangling Images weekly
  • Steps to cleanup services
  • Bash into containers
  • Training
  • Dockerizing a set
View terminal
\x1b[30mblack\x1b[37mwhite
View blink.js
@cromwellryan
cromwellryan / All.md
Last active Jul 14, 2016
Dayton Clean Coders 2016-07-13: FizzBuzz kata in Unfamiliar Languages using https://repl.it
View All.md
View dcc-go.md
  1. $GOPATH is the well known place where go looks for things and installs built things.
  2. go install <path> <path> is relative to $GOPATH\src.

For example, the following will attempt to compile code found in $GOPATH/src/my-app:

$> go install my-app
  1. go install doesn't care if package <name> matches the fs path structure.
  2. When the name of a package is main, that package ends up in $GOPATH/bin
You can’t perform that action at this time.