Recently I was asked how debugger console behaves in ruby 1.9 and I just didn't know answers right away.
Can you believe, once my loved tool in early days 2006 and now I barley remember how to use it.
Anyhow, we can blame doing all the years test/behaviour driven development, what has significantly reduced debugger value to the point I start forgetting it :-)
Nice, after days waiting I finally managed to get Euruko 2010 ticket!
Euruko tickets sold out within 20h, wow and did I told you I bought plane ticket a month ago already :-)
Anyhow, see you all there!
There are quite a bit changes between bundler 0.8 and 0.9 and it took a bit time to figure out what has changed.
First, there seems a new way of running it, now run "bundle" instead "gem bundle".
Second, if you need to unpack gems to vendor, just add path:
bundle install vendor/gems
I started to unpack them to application root, so I can access bin files more easily:
bundle install .
Anyhow, the new bundler 0.9 has a bit more lighter work-flow than 0.8.
I have used and contributed code for two big Rails cms frameworks: adva-cms.org and ubiquo.me.
I give a very quick overview. In high level they both are similarly built on top of rails engines and providing tools for speeding up dev speed for creating more classical websites with common feature requirements. However, the scope of two are actually a bit different. Adva-cms has broader scope and provides features such as photos, articles, newsletters and so on, but Ubiquo currently focuses on providing tools for creating quick admin interfaces.
Even though they both provide real value on the table, they are on the same time quite a big dependency itself (hint-hint Rails 3 :-) I know, we can blame the Rails world itself for moving so fast that the hot code in morning is already badly outdated for evening :-)
However to minimize this, I do believe that CRMs should embrace even more eagerly what rails community offers. For example, why nowadays Adva and Ubiquo still has its own access controls when we have declarative authorization out there. Or let's put it other way, why we don't see CMS custom made access controls competing and winning openly at ruby-toolbox.com?
Anyhow, I hope new Rails 3 brings more modularity on the whole Rails community but probably it won't go as far as Pancakes goes.
I can't believe what scam and spam has done with people at Craigslist. It's scary and sad.
I wanted to rent a flat in Barcelona and I found one, but the current flat owner told me quite directly that I'm not renting it for me because my e-mail, my skype call and my mobile phone call looks like scam to him!!!
Excuse me, WHAT???
I was totally speechless, I felt really-really stupid to prove him that I have real intention to rent it. However he just didn't believe me at all.
Crap, this is really some new level stuff for me and it looks it's somehow part of Craigslist culture nowadays. Anyhow we can really declare that spammers and scammers have won the Craigslist long time ago :-(.
I spent some hours figuring out why nginx did served static files without problems but rails on passenger were giving me happily "403 Forbidden" error with log entry:
2009/07/25 21:07:03 [error] 2393#0: *2 directory index of "/var/apps/gripesegg/public/" is forbidden, client: 87.119.178.242, server: gripesegg.com, request: "GET / HTTP/1.1", host: "gripesegg.com"
Google suggested I should look over rails app permissions, what I did several times without much success.
There must be some other issue and luckily I wasn't only one with this issue. Turns up, I had at nginx site config file either remove "location /" block or re-specify "passenger_enabled on" inside it.
Wrong way: Will give 403 Forbidden
server {
listen 80;
server_name wikicards.org;
access_log /var/log/nginx/wikicards.access.log;
passenger_enabled on;
location / {
root /var/apps/wikicards/public;
index index.html index.htm;
}
}
Correct way: Add "passenger_enabled on" to the block or remove it as I did:
server {
listen 80;
server_name wikicards.org;
access_log /var/log/nginx/wikicards.access.log;
passenger_enabled on;
}
I hope this tip will save some time for someone.
I fonud nice tip to show current git branch like this:
user@group:~/apps/myapp:master$
At your ~/.bashrc change PS1 value to:
PS1='${debian_chroot:+($debian_chroot)}\u@h:\w$(__git_ps1 ":%s")\$ '
Updated 28.11: I changed git branch indication to a new location (one line):
PS1='${debian_chroot:+($debian_chroot)}\u@\h$(__git_ps1 "[%s]"):\w '
what will produce:
user@group[master]:~/apps/myapp
Enjoy!
Updated 2009.04.09: Nowadays I'm using zsh :-)
note: now I'm adva new dev, so I might not be very objective :-)
If you have used Radiant or any other ror based cms then try out very new project Adva CMS.
It's kind of next evolution compared to Radiant.
Firstly, it keeps your main app directory clean for your own project, so upgrading Adva is a bit easier than with other cms where all app files are together with cms ones.
Secondly, admin main panel is trying to be as agnostic as possible. So all engines are visually equal to other ones such as blog, forum or wiki.
However adva cms is not ready yet. It's still alfa but under active development. By the way, it has got already over 2000 specs :-)
Anyhow, I'm already big fan of adva cms and trying to help as much as I can to develop it.
The idea is coming from Jay Fields blogpost about distributed developers and its viability.
As we know office devs usually got much faster communication cycles and thus distributed devs are often behind the flow.
However
the game change quite a lot when all project members are distributed.
Suddenly everybody have to use same communication channels, thus it's
much easier for each member to be in the flow.
There are lot's of ways and tips to make distributed development more viable, therefore I got the idea to create dedicated networking for people who would like to become a bit more efficient distributed developer and find others who are a like.
Rails Rumble is good place to start coding and trying things out.
We didn't get very far with features but at least here is the beginning:
Welcom to Gitnation!
