So let’s say you’ve got a new use case for couchbase.  You want a new bucket with new views.  You’ve got existing couchbase infrastructure.

Do you add a new bucket to that cluster?  If things begin to suffer performance-wise, do you add new nodes to the cluster?

Or do you create start off by creating a new cluster for this new bucket and minimize interfering with the existing clusters?  Any tips?

apijoy:

If it wasn’t for your frivolous lawsuit, I’d never have found craiggers.com.

http://news.cnet.com/8301-1023_3-57479344-93/craigslist-sues-padmapper-for-mass-harvesting-listings/

Now go back to your antipattern cave and continue to stymie.  

First, I was trying to solve the colors/ESC[ problems when piping colored grep into less, and this helped me solve it:

http://excid3.com/blog/how-to-fix-esc-in-your-terminal/

(Added export LESS=”-eirMX” to my ~/.zshrc)

Then I wondered if I could get the same nice coloring in git, and sure enough:

http://git-scm.com/book/en/Customizing-Git-Git-Configuration#Colors-in-Git

(git config —global color.ui true)

But I use mercurial at work, surely mercurial has this… yep!

http://mercurial.selenic.com/wiki/TipsAndTricks#Generating_color_diff_output

(add the following to your hgrc, although for most diffs I just use an external diff tool like meld or gvimdiff:

[defaults]
# suppress noisy extdiff header message
cdiff = -q
[extdiff]
cmd.cdiff = colordiff
opts.cdiff = -uprN

Now I can see the world in delicious retina color ;D