GitHub User: denispeplin
With rvm, startups also much faster when optimization patches are used, for example ruby-1.9.3-p392-railsexpress or ruby-2.0.0-p0-turbo.
Excelent article: AngularJS for jQuery Developers
Joosy seems does not as easy to use as declared.
You can try to implement Angular's "Hello world" in jQuery. That's where jQuery solution will be more complex, and that's why I like Angular.
I created a gist with another example: https://gist.github.com/denispeplin/5096725
Exactly. It is not easy to start writing applications in some js framework while jQuery suits most use cases really well and it so easy to start with. But I found that Angular can solve some tasks in a way that easier to implement than jQuery equivalent. Most important, you don't have to setup full-stack application for Angular. Just include it and start using.
Me too. I'm just starting with Angular, but already can't imagine myself doing something in Ember or Backbone :)
Thunderbolt Labs article Why we don't use a Rails template
Installing Ruby on CentOS:
How to use Puma by default: (by running just rails s instead rails s puma): http://stackoverflow.com/questions/14146700/how-to-change-the-default-rails-server-in-rails-3/14911994#14911994
rails s puma
No I18n yet.
Devise is almost ready to use with Rails (look at 'rails4' branch in its repository), but including ActionController::Live crashes the application.
For the moment, solution is to move events action to separate controller.
Tried to implement this episode, it works!
Not such a big overhead adding Redis server.
Try Sympathy editor, maybe it will work: https://github.com/captn3m0/sympathy
Too many mac-specific stuff everywhere in the Ruby world. Sad. But in this specific case it is the Chrome fault. It is actually unable to launch external editor in Linux.
That is the issue #1 with server-side processing. Whatever server-side search will be implemented, anyway it will searching against server-side 'look' of the data. Client-side search will find exactly what user wants even in complex cases.
So I would rather implement some pre-filtering by date or other parameters and pass all that filtered data to client-side.
Other issues, that not covered in this episode, like sorting on associated table values, can be solved relatively easy using joins.
Great topic, I waited for this a for a long time. Thanks!
One thing that I missing in this episode: Redis was described instead of PostgreSQL. Going to figure out how to do this with pgsql. Maybe this gem is applicable: https://github.com/ryandotsmith/queue_classic
Controller looks ugly? Move stuff to separate class.
Command is too long? Make an alias.
Tried this. Looks great, but requires a lot of effort to fit in my environment (I18n, etc.).
And another gem, closure_tree: https://github.com/mceachen/closure_tree
"Closure Tree is a mostly-API-compatible replacement for the ancestry, acts_as_tree and awesome_nested_set gems".
Rails gem: https://github.com/bokmann/fullcalendar-rails
That is great approach, thank for the link. Unfortunately, in my current project I have two databases, and some models are connects to second database, so this approach does not work.
This fixes encoding issue, thanks!
And another issue.
private_pub.ru should contain:
Taken from https://github.com/faye/faye/issues/128
gem 'thin' should be in Gemfile for this to work:
rackup private_pub.ru -s thin