some tools for diagrams in software documentation
| #printf | |
| RUN printf '#!/bin/bash\n\ | |
| echo hello world from line 1\n\ | |
| echo hello world from line 2'\ | |
| >> /tmp/hello | |
| #echo | |
| RUN echo -e '#!/bin/bash\n\ | |
| echo hello world from line 1\n\ | |
| echo hello world from line 2'\ |
| #!/bin/bash | |
| ##################################################### | |
| # Name: Bash CheatSheet for Mac OSX | |
| # | |
| # A little overlook of the Bash basics | |
| # | |
| # Usage: | |
| # | |
| # Author: J. Le Coupanec | |
| # Date: 2014/11/04 |
| # A little Meteor CheatSheet about Iron-Router. (updated on a weekly basis) | |
| # Check our Studio: https://gentlenode.com/ | |
| meteor add iron:router | |
| meteor update iron:router | |
| # Iron Router > Configuration |
ror, scala, jetty, erlang, thrift, mongrel, comet server, my-sql, memchached, varnish, kestrel(mq), starling, gizzard, cassandra, hadoop, vertica, munin, nagios, awstats
Originally published in June 2008
When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.
To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.
Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.
| # -*- Conf -*- | |
| [color] | |
| branch = auto | |
| diff = auto | |
| status = auto | |
| showbranch = auto | |
| ui = true | |
| # color.branch | |
| # A boolean to enable/disable color in the output of git-branch(1). May be set to always, false (or |
| # Build Passes | |
| curl -d "room_id=ourRoom&from=BuildBot&message=Build+Status:+Passing&color=green" https://api.hipchat.com/v1/rooms/message?auth_token=AUTH_TOKEN_HERE&format=json | |
| # Build Fails | |
| curl -d "room_id=ourRoom&from=BuildBot&message=Build+Status:+Failing&color=red¬ify=1" https://api.hipchat.com/v1/rooms/message?auth_token=AUTH_TOKEN_HERE&format=json |
