username: pickmyride
pw: paynearme326
api Key: 3chtf5zzrkf82xubzv9t2wcn
origin git@github.com:lauraeci/PickMyRide.git
db:create:all
db:migrate
oops
I meant... rake db:create:all
and... rake db:migrate
There's a hack night at Mixbook next week. With any luck, we can meet up and work on this project some more: http://www.meetup.com/rubymeetup/events/174037822/
Code school has en episode on ember, if you want to give it a trial run, they have a two day hall pass to try it out for free otherwise its a monthly fee.
ActiveResource was removed from Rails 4 and is now a separate gem, it looks cool because we can hide the details of the request and access our api similarly to how we use ActiveRecord.
I went through the first level of codeschool for Ember tonight, and it finally dawned me that Ember is a full-fledged MVC framework for JS. I was not aware of this before as I've never really spent any time with it. As such, I'm wondering just how deep I want to wade into learning a JavaScript framework for a Ruby on Rails project. And I'm a bit confused at the moment... Are we just going to use Rails for the API?
I was thinking of Using ActiveResource to get data from the Edmunds API and Ember for the responsive aspect. We don't have to use all of Ember, but in my experience it is very common for Rails shops to use a JavaScript framework like Ember, Backbone, or Angular. In my current job we use Angular, so its a good thing to know how it works with a Rails project. I think all the Business logic should be done in Rails not JavaScript, so authenticating a user, storing user choices, and the logic to decide what car to pick, whether its AHP or other. Does that sound good to you? I can work on the Ember part unless other people are interested since I want to get better at that.