You’ve come a long way, congratulations! At this point, you should feel comfortable with building new Rails applications, modelling data, and working with forms. This project will require you to put all your newfound knowledge to the test. It should serve as a great portfolio piece for what you’re capable of. It’ll take some thought and time but it’s certainly within reach of your skills.
You’ll be building Facebook. As usual, any additional styling will be up to you but the really important stuff is to get the data and back end working properly. You’ll put together some of the core features of the platform – users, profiles, “friending”, posts, news feed, and “liking”. You’ll also implement sign-in with the real Facebook by using Omniauth and Devise.
Some features of Facebook we haven’t yet been exposed to – for instance chat, realtime updates of the newsfeed, and realtime notifications. You won’t be responsible for creating those unless you’d like to jump ahead and give it a shot.
You should write at least a basic set of integration tests which let you know if each page is loading properly and unit tests to make sure your associations have been properly set up (e.g. testing that
User.first.posts works properly). Run them continuously in the background with Guard (See the Ruby on Rails Tutorial Chapter 3.7.3).
This project will give you a chance to take a relatively high level set of requirements and turn it into a functioning website. You’ll need to read through the documentation on Github for some of the gems you’ll be using.
Keep the following requirements in mind. We’ll cover specific steps to get started below this list:
#current_usermethods. See the Railscast (which uses Rails 3) for a step-by-step introduction. The docs will be fully current.
letter_openergem (see docs here) to test it in development mode.
$ rails new odin-facebook --database=postgresql, initialize the Git repo, and update the README to link back to this page.
db/seeds.rbfile, which gets run if you type
$ rake db:seed.
Send us your solution so we can show others! Submit a link to the Github repo with your files in it here using any of the methods listed on the contributing page. Please include your partner’s github handle somewhere in the description if they would like attribution.
|Jason McKee’s solution||Live|
This section contains helpful links to other content. It isn’t required, so consider it supplemental for if you need to dive deeper into something.