Monday, December 10, 2012

Todoist : Solving cross domain security policy


From https://todoist.com/API/help

Solving cross domain security policy [top]

You cannot use AJAX to directly communicate with Todoist, this is due to browser security policy. You can solve this by communicating with Todoist using a script tag:
var script = document.createElement('script');
script.type = 'text/javascript';
document.getElementsByTagName('head')[0].appendChild(script);
The response data will look like this (callbackFunction will be called):
callbackFunction({ JSON data here });

Sunday, December 2, 2012

GNU Screen Cheat-Sheet

Taken from http://neophob.com/2007/04/gnu-screen-cheat-sheet/
Basics:
–ctrl a c           -> cre­ate new win­dow
–ctrl a A           -> set win­dow name
–ctrl a w           -> show all win­dow
–ctrl a 1|2|3|…   -> switch to win­dow n
–ctrl a ”           -> choose win­dow
–ctrl a ctrl a      -> switch between win­dow
–ctrl a d           -> detach win­dow
–ctrl a ?           -> help
–ctrl a [           -> start copy, move cur­sor to the copy loca­tion, press ENTER, select the chars, press ENTER to copy the selected char­ac­ters to the buffer
–ctrl a ]           -> paste from buffer
How to start screen:

–screen –DR            -> list of detached screen
–screen –r PID         -> attach detached screen ses­sion
–screen –dmS MySes­sion -> start a detached screen ses­sion
–screen –r MySes­sion   -> attach screen ses­sion with name MySession
Advanced:

–ctrl a S       -> cre­ate split screen
–ctrl a TAB     -> switch between split screens
If you cre­ated a new split screen, the cur­rent win­dow is empty. either select an exist­ing win­dow (ctrl a ”) or cre­ate a new split screen (ctrl a n).

–ctrl a Q       -> Kill all regions but the cur­rent one.
–ctrl a X       -> remove active win­dow from split screen
–ctrl a O       -> logout active win­dow (dis­able out­put)
–ctrl a I       -> login active win­dow (enable output)

Thursday, November 29, 2012

Sphinx fails to start with rake ts:start or rake ts:rebuild

$ rake ts:start
Failed to start searchd daemon. Check ../log/searchd.log.
Failed to start searchd daemon. Check ../log/searchd.log
Be sure to run thinking_sphinx:index before thinking_sphinx:start
Almost always is the case for me that searchd is already running / orphaned and needs to be killed. Run
$ps -ax | grep searchd
shows that its already running
49630 ttys000    0:00.06 searchd --pidfile --config ../config/development.sphinx.conf
49644 ttys001    0:00.00 perl /usr/local/bin/grep searchd
and kill it
$kill -9 49630
Voila!

Friday, November 2, 2012

Is there a way through which I see which mysql queries are fired from ActiveRecord in rails console?

http://stackoverflow.com/questions/4667316/how-to-see-mysql-queries-in-rails-console

Yes, this can be achieved through redirecting rails log to standard output.

Write these at your console prompt:

ActiveRecord::Base.logger = Logger.new(STDOUT)
ActiveRecord::Base.connection_pool.clear_reloadable_connections!
Furthermore, you can put these lines in ~/.irbrc file, so that each time you don't need to manually write these 2 lines:

require 'rubygems'

if ENV.include?('RAILS_ENV') && ENV["RAILS_ENV"] == 'development'
    ActiveRecord::Base.logger = Logger.new(STDOUT)
    ActiveRecord::Base.connection_pool.clear_reloadable_connections!
end