#Council of Chiefs
9:00PM November 3, 2012
Camp Lazarus
4422 Columbus Pike
Delaware, OH 43015
Goal of the Meeting: To make decisions regarding the specifics of Conclave 2013
| find ~ -name '*.log' -print0 | xargs -0 -L1 stat -f'%z %N' | sort -rn | tee fat-logfiles.txt | head | |
| awk '{ total += $1 } END { printf "total: %5.2f MiB\n", total/1024/1024 }' < fat-logfiles.txt |
| # I don't really see any services here. What I see is: | |
| # - Normal HTTP boundary stuff (params flash, redirect). | |
| # - Model creation and retrieval. | |
| # - Warden manipulation, which is an odd done but smells like boundary. | |
| # | |
| # I left all of the HTTP boundary stuff in the controller (and only the | |
| # controller). I moved the model creation/retrieval into simple class methods | |
| # in the models. I moved the warden manipulation stuff into | |
| # ApplicationController (with caveats that I'll discuss inline). | |
| # |
#Council of Chiefs
9:00PM November 3, 2012
Camp Lazarus
4422 Columbus Pike
Delaware, OH 43015
Goal of the Meeting: To make decisions regarding the specifics of Conclave 2013
This configuration works with Upstart on Ubuntu 12.04 LTS
The reason why it needs to be done this way (i.e. with the pre-start and post-stop stanzas), is because Upstart
is unable to track whever Unicorn master process re-execs itself on hot deploys. One can use it without hot-deploys
and run Unicorn in foreground also, it then only needs one exec stanza.
This presumes you are not using RVM, so no voodoo dances.
| Today I ran a quick twitter poll asking: "What is the state of the art | |
| in Ruby SOAP clients". | |
| Savon (http://savonrb.com/) was by far the big winner with 29 | |
| recommendations. | |
| Surprisingly Soap4r actually got 6 votes, but most were accompanied by | |
| comments like "the last time I used SOAP". It was also the only entry | |
| that got negative votes (3) with comments like "soap4r is broken and | |
| crap by the way". |
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.| # general support for dumping the post db:seed db to a hash | |
| # | |
| def App.db_names | |
| result = | |
| Mongoid.session(:default). | |
| with(database: :admin). | |
| command({listDatabases:1}) |
| #!/bin/bash | |
| # License: Public Domain. | |
| # Author: Joseph Wecker, 2012 | |
| # | |
| # -- DEPRICATED -- | |
| # This gist is slow and is missing .bashrc_once | |
| # Use the one in the repo instead! https://github.com/josephwecker/bashrc_dispatch | |
| # (Thanks gioele) | |
| # | |
| # Are you tired of trying to remember what .bashrc does vs .bash_profile vs .profile? |
| class Organization | |
| def to_param | |
| "42" | |
| end | |
| def saved? | |
| rand > 0.5 | |
| end | |
| end | |