tail -f log/development.log
The tail command is very helpful. It is very important for a newbie like me to view and understand logs.
If I want to save the logs for later viewing starting from the time I tailed, I redirect the output to a text file:
tail -f log/development.log > ~/Desktop/some_file_name.txt
Tail is not available in windoze but one can install software to do just this. In my personal experience, the logs tells a lot about what your doing wrong, instead of relying on the online tutorials or screencasts that are usually outdated. It is through looking at the logs that I was able to find out why the tutorial wasn’t working the way I wanted it. You see I usually have several resources and try to mix them up together. Even though the tutorial has a warning that, this will not work in rails 2.x, still my curiosity wanted to make it work.
Sure I could googlize, but sometimes I see it as an advantage to be offline than being online, as this forces me to understand the inner workings of rails and really get on reading the documentation. There’s this feature of NetBeans IDE I appreciate, it makes documentation accessible. I actually found this out by accident, I just have to press Ctrl + Shift then click on the method i would like to find out how to use, and a window will open to show a nice looking docu.tags: RubyonRails category: tips
- OCD-free ruby-1.9.2-p180 on Ubuntu 10.10
- Install CDR King Zen PC Camera on Linux
- Wirble on Windoze without Rails
- PCLinuxOS distro hopper stopper, 2009 Beta 1 is out
- Daemonize Your Gems in PCLinuxOS