No Debian/Ubuntu existe um jeito simples de fazer um upgrade da versao 9.2 para a versao 9.3 do PostgreSql com os comando pg_upgradecluster (http://manpages.ubuntu.com/manpages/jaunty/man8/pg_upgradecluster.8.html).Basta seguir o procedimento abaixo:sudo apt-get install postgresql-9.3sudo /etc/init.d/postgresql stopsudo pg_dropcluster --stop 9.3 mainsudo pg_upgradecluster 9.2 mainApos isso, e possivel rodar o comando pg_lsclusters para verificar que a versao 9.3 esta ok. Pessoal,fiz uma GEM para consumir a API do Emailmarketing da Locaweb.O Github e esse: https://github.com/fabioperrella/locaweb-emailmarketingEsta publicado no rubygems: https://rubygems.org/gems/locaweb-emailmarketingSugestoes serao bem vindas! Vou postar isso aqui pois sempre esqueco qual o arquivo que deve ser alterado:sudo vim /etc/NetworkManager/system-connections/Wired\ connection\ 1[802-3-ethernet]duplex=fullmac-address=78:2B:CB:C4:69:52[connection]id=Wired connection 1uuid=eba66e39-b7d1-4ce8-a79d-60208a94f966type=802-3-ethernettimestamp=1394655259[ipv6]method=auto[802-1x]eap=peap;identity=[USERNAME]phase2-auth=mschapv2password=[PASSWORD][ipv4]method=auto *obs: testei isso rodando no Ubuntu 12.4, nao tenho certeza se funciona no Mac e no WindowsCom este hook o nome do branch sera colocado no comeco de todos os commits do gitPor exemplo se fizer isso no branch [historia_1]git commit -am "lala popo"A mensagem gravada sera "[historia_1] lala popo"Segue o passo a passo de como configurar o git para isso:- Se estiver usando o git acima da versao 1.7.1, e possivel deixar o hook global deste jeitogit config --global init.templatedir '~/.git_template'- Depois disso, criar o arquivo abaixo~/.git_template/hooks/prepare-commit-msg- Colocar o conteudo abaixo:#!/bin/bashFILE=$1if [[ "$git_status" =~ On\ branch\ ([^[:space:]]+) ]]; then BRANCH_NAME=${BASH_REMATCH[1]} test "$branch" != master || branch=' 'else # Detached HEAD. (branch=HEAD is a faster alternative.) BRANCH_NAME="`git describe --all --contains --abbrev=4 HEAD 2> /dev/null || echo HEAD`"fiecho $1if [ -n "$BRANCH_NAME" ] && [ "$BRANCH_NAME" != "master" ]; then sed -i.bak -e "1s/^/[$BRANCH_NAME] /" $FILEfi- Salvar o arquivo e colocar permissao chmod 755A partir desse ponto, todos os repositorios clonados e inicializados terao este hook, para os ja existentes, precisa rodar o comando git init que carregara o hook global. According to ruby2.3 changelog, the class "Net::Telnet" was removed from the ruby-core and was "gemified"Thu May 21 15:41:45 2015 SHIBATA Hiroshi <hsbt@ruby-lang.org> * lib/net/telnet.rb: gemify net-telnet. [Feature #11083] * gems/bundled_gems: added net-telnet to bundled gems.To use it, just add the gem "net-telnet" to Gemfile! Uma dica simples e facil para aumentar a velocidade dos testes no Rspec com PostgreSql e seguir as instrucoes nesse link:http://www.postgresql.org/docs/current/static/non-durability.htmlobs: nao fiz o 1o item da lista (RAM disk)No meu caso os testes que rodavam em 4min e 10s cairam para 56s !!So nao use essas configuracoes em producao pois o risco perder dados e alto! Last week, at my job, we were trying to find the root problem that was killing one of our applications. It is a rails app running on Debian, and we had some clues about the problem:- looking at New Relic errors, we saw many errors like "getaddrinfo: Name or service not known"- looking at Unicorn logs, there were a lot of "too many open files" errorsIt seemed the application was being killed by these errors.We thought that the server may have some network problems, as this could explain the "Name or service not known" error which is an error that happens when some domain can't be resolved with DNS.But after some research, we remembered this kind of "too many open files" error is related with the number of open files in the filesystem. It