gem i request-log-analyzer
request-log-analyzer log/production.log --output HTML --file tmp/log_report.html
In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:
http://techcrunch.com/2007/08/11/facebook-source-code-leaked/
It became a big deal:
http://www.techmeme.com/070812/p1#a070812p1
The two files are index.php (the homepage) and search.php (the search page)
from http://tips.naivist.net/2006/02/02/word_to_markdown_converter/ Word to Markdown converter
Some smart people who didn’t want to teach users how to code in HTML invented Textile markup language
Someone more lazy invented MarkDown syntax which is much easier to learn. MarkDown is really nice for small content management systems, blogging engines etc.
For instance, to mark text as bold, you write the “bold text” like “bold text”. Other rules can be found in the syntax page.
However, when you have a MS Word document with several pages of bolds, italics and lists, you don’t really want to re-code all the markup.
#!/usr/bin/env ruby | |
# Put this file in the root of your Rails project, | |
# then run it to output the SQL needed to change all | |
# your tables and columns to the same character set | |
# and collation. | |
# | |
# > ruby character_set_and_collation.rb | |
DATABASE = '' |
Please behave in a polite, considerate and inclusive manner in the channel at all times. People volunteer their time in the channel to help people like you with your Rails problems and some respect (in both directions) will go an extremely long way.
These rules are in place so that you can get the quickest and best support from #rubyonrails.
Rule #0: Show rather than tell. Explaining your problem with code, stacktraces or errors is always preferred to explaining it with just text. Show us what's happening, rather than telling us.