Customer Reviews

RailsSpace: Building a Social Networking Website with Ruby on Rails (Addison-Wesley Professional Ruby Series)

5 star:		(16)
4 star:		(4)
3 star:		(2)
2 star:		(3)
1 star:		(2)

 

 

RailsSpace does an excellent job of teaching Ruby on Rails through a hands-on, real world application. If you are like me then you probably cringed at the thought of yet another social networking site. However, after reading through the first part to this book my apprehensions were put at ease. The authors explained in the opening chapter that "There's a tension in any educational book between the two extremes of pure tutorial and pure reference. We land firmly on the tutorial side of this spectrum--" The audience for the book is anyone beginning with Ruby on Rails. This book assumes no prior knowledge of Rails or Ruby, and sticks to that through the entire book. Each chapter walks you through the process of creating RailsSpace, while also teaching you best practices and some of the nuances of Ruby and the Rails framework.

This book is broken into two main parts, Foundations and Building a Social Network, with each part comprising several chapters each.

Foundations
Getting Started
With the introduction out of the way, it is time to jump into building the application. This chapter assists you in getting Ruby on Rails and its dependencies on your platform of choice, and then gives instruction for setting up your development environment. Once all of the pieces are in place they move to setting up your rails application, and how to get started with your first pages. They use rails generator to create the controllers and give you an idea of the default routing of a Rails application. The rest of the chapter spends some time building views and using embedded ruby to work with your templates. For the beginner to Ruby or Rails, this part is valuable for the rest of the application. They teach the basics of Ruby and introduce you to instance variables, hashes, and symbols. It isn't practical for them to cover everything, so they also give you direction on finding answers to questions that might arise. The first place to look is always the API. We have the basics down, we have created our application, generated some controllers, and put our navigation into place.

Modeling users
What good is a social networking site without any users? Here we are introduced to setting up our models in our application. This chapter touches on defining your schema through the use of migrations. You build the migration, run the migration, and then work within the model to create your validations. They spend some time with the validations and show you how to use the default helper methods or extend the validations to be more powerful and suit your needs. Now we have a place to store our users, lets move on to the process of letting them become part of the community.

Registering users
This chapter focuses on the process needed to allow a user to register to RailsSpace. We are introduced to some more Rails magic as we build the User controller and the views. We start first with the view of the registration form and learn how to use Rails helpers to generate our form fields and error messages. Next we look at the action that handles the response to the user. This involves the validation, flash error messages, and flash notifications. With the registration in place, we take a pause to look at something very important in any software development: testing.

Getting started with testing
Before we move any further we need to make sure things are responding as they should be. Testing things yourself may seem practical when the application is small, but as it expands testing proves to be extremely useful. We create tests for the database connection, our site controller, the registration process, and testing of the User model. Testing allows us to check all important aspects of our application. We can simulate the processes of a user and assure that we receive the proper response and that everything stays fine tuned. This chapter sets the foundation for the rest of the application as we expand and create new tests. We have tested everything is working as planned, now let's handle the process of logging in.

Logging in and out
Authenticating a user may seem simple at first glance, but there are often times steps that are overlooked in the process. This chapter attempts to cover all bases of making the login process painless. We learn how to setup the database for sessions and how to utilize them in our application. The sessions allow us to keep state of a user and their privileges. This also means that we need to protect our pages and some of our actions. They take the time to cover friendly URL forwarding, letting a user be directed back to any page after they login. Again, we run tests as we build more pieces onto the application. The end of the chapter is spent looking at the current code and refactoring to keep neat and tidy with the DRY principle. Just as with testing, this is also a very important part to the application and something the authors spend time doing with each and every piece of the application. We are also introduced to some more helpful Ruby nuances such as boolean methods and the bang! methods. A user has the ability to login, but we can take it one step further.

Advanced login
Users now have the ability to login. It is time to extend the login by allowing the application to remember the user. This chapter is spent on building the remember me functionality. This involves extending several aspects including the User model, the user session, and the authentication cookie stored in the browser. Since we are updating different aspects we take the time to extend our tests, assure our previous tests still work, and refactor some more of the code that we are building.

Updating user information
With login out of the way it is time to look at allowing users to interact with the website. The first part to this interaction is allowing them to update their details and information. This chapter discusses the process of allowing a user to change their email or update their password. The username is left untouched, as we will be creating a permalink with their username.

Our foundation is set. We have come a long way in just a few chapters, now it is time to extend our solid foundation.

Building a Social Network
Personal profiles
In the last chapter we allowed the user to update their email and password. Now we extend that to let the user create their own profile or spec. This allows a user to share all of their most intimate details one a single page. We look at building the user profile to be modular and utilize the same views for the public face and administrative face. We are introduced to some more rails helpers and some advanced routing techniques named routes. The user profile is in place, now it is time to create the pieces that allow all of your friends, teachers, aunts, and enemies to find you.

Community
The next few chapters will be spent building the central hub that will allow you to interact with the community as a whole. The first part addresses setting up the Community controller and setting up sample data to test our features with. Our first piece to the community controller is allowing you to browse users by an alphabetical index. This shows us some more options of the find method in ActiveRecord and how we can implement pagination and a summary in our results. Browsing by an alphabetical index is helpful, but lets move on to allow search and browsing by A/S/L.

Searching and browsing
Here we are introduced to plugins and using Ferret to help us with our search. As with the alphabetical listing we set it up to allow pagination within the results. We then setup a custom form to allow the user to search by age and sex. This utilizes the same views to return the results and allow pagination. Now we look at the location part. This is a little more advanced as it uses a GeoData database and a proximity search that allows you to find other users within a certain mileage of your current zip code. This concludes giving us all of the tools we need to find any information we need related to our users.

Avatars

What good is a name without a face? This chapter discusses several new aspects. The first is using a model that doesn't connect to a table in the database. The second is handling image uploads and resizing. We create the interface and allow for the user to upload, save, or delete their picture.

Email
This chapter introduces us to Active Mailer, an aspect of Rails that allows us to send emails. We will setup a model that extends Active Mailer, configure our server to send email, and create the necessary links to allow users to contact their friends. We create a double-blind email system that allows the users to contact each other without exposing their actual email address. Naturally, we add the methods that allow you to correspond with the user. Once it is all in place, we take a look at some new testing methods that allow us to simulate the sending of emails without filling our inboxes.

Friendships
Friendships live at the core of creating a social networking system. After all, the more friends you have the more popular you must be in real life! Again, we are introduced to some new modeling techniques in this chapter. In order for a user to be a friend with another user, we must create the relationship accordingly. This involves having a Friendship model that has the current user ID, and the friend ID. Using has_many :through we are able to recursively look through this table to keep track of the friendships and their statuses. As with everything else, we take the time at the end to test and refactor.

RESTful blogs
This chapter throws an advanced topic our way, that of creating RESTful URLs for our application. There is much to be explained here, so I will avoid repetition. REST allows you to create neat URLs while also keeping your CRUD actions neat and tidy. This is important as we allow the users of our system to create blogs. Each user can have their own blog. Each blog can have many posts. Each post can have many comments (depending on how many friends you have). Using REST and map.resources to create our URLs we can utilize several Rails helper methods as well as give us a structure like http://www.example.com/user/name/blog/blog-title/blog-comments/. Though that may seem long and convoluted, it also allows us to utilize the power of the respond_to block to allow for RSS in each section without a lot of hassle.

This is just a small glimpse at what this chapter covers in regards to REST. This proved to be one of the most useful chapters for me. Utilizing this power in rails also warrants some new testing functionality to check for. We test to make sure everything is working, then move to implementing some Ajax into our application.

Blog comments with Ajax
We wouldn't be very web 2.0 without Ajax. This chapter shows how to implement Ajax into our commenting system. We use both Ajax requests to submit the comments, and animation to toggle the display of the comment form. Rails comes with Prototype and Scriptaculous built in, so those libraries are used for the interaction. This is the only chapter that rubbed me the wrong way. I know that productivity is important, but I also don't like the way that Rails implements JavaScript inline all over the place. I am in the camp of unobtrusive JavaScript, so this seems like going backwards to me. Sure, it is simple to implement with Rails helpers, but the output is simply horrendous. The chapter still has important aspects, I just feel they could be built in an unobtrusive manner, especially when you are using JavaScript to toggle the display of your comment form.

What next?
This chapter focuses on deployment of our application and the options available to us. It also addresses the issues of scaling, both with hardware and software, and administrating your Rails application.

I may seem cynical about social networks, but this truly book pays attention to the small details. Building a social network is a great tutorial that covers many aspects of Rails and building your own application - no matter what it is. It has several callout boxes that give more explanation where it is needed. It discusses the importance of testing. It shows the importance of refactoring. All of this comes together to make a great reading experience and knowledge gained. If you are a Rails professional, there might not be a whole lot new for you, but if you are just beginning Rails this is an excellent full-blown tutorial. Even if you don't want to create a social networking site, the foundation and principles set in this book will give you the knowledge needed to start building your own application.

For this beginner/intermediate programmer struggling to become a Ruby and Rails expert, RailsSpace strikes a perfect chord.

I have been working through the Safari version of the book until receiving my hard copy yesterday.

I would highly recommend this as the first book on learning RoR after a pure Ruby book such as

Programming Ruby: The Pragmatic Programmers' Guide, Second Edition"(known in the community as the Pick Axe)

or

Beginning Ruby: From Novice to Professional (Beginning from Novice to Professional)"

two excellent books on Ruby which I found out the hard way is best learned before tackling Rails.

One of the many things that make this book a pleasure to study is the code just works as is. For those of you who have suffered through many Rails books that in the rush to publish have you constantly referring back to 5, 6, or more of errata, it is such a nice surprise to enter code and it just works. I am currently running Ruby 1.8.6 and 1.2.3 the current versions and have had to refer to only one example of errata in the first half of the book.(p.24 gemserver should be gem_server). Kudos to the technical editor for a "getting it correct."

The authors' programming style(s) are easy to read while following and teaching the Ruby/Rails community practices. The book uses output examples after each snippet of code so you can follow along not wondering if what you just did worked.

The example app you produce while working through RailsSpace is not YASNS (Yet Another Social Networking Site) rather a (LBERBPS) Learn by Example Rails Best Practices Site. It was fun for me as I was tired of shopping cart, and book/music store examples.

I don't know how to put it into to the right words, but this books code flows.

I always enjoy the rare book that sets a standard of excellence, and that is what puts this book at the top of my Ruby on Rails Library.

This book is a must have for a beginner Ruby on Rails programmer. It covers all of the basics of building a social networking website in depth. Specifically Railspace goes over: registration, login, user relationships (friends - this is quite complicated for the beginner), search, image uploads, and more... While you could technically use Google and the many Rails forums to find the answers found in this book, using this book is both a time saver and headache preventer (if it were around when I started development on my website).

On a related note, I've read both this book and Practical Rails Social Networking Sites. In my opinion, you should get both books. However if you have to choose one it would depend both on your skill level and taste. Would you rather have more subjects covered with less material, or would you like less subjects being covered more in depth. If you want more detail or if you are just starting ROR development, then I think RailsSpace wins. Still I would get the other book too since they're both pretty cheap (at Amazon.com)

The thing I like most about this book is that its readable. You can learn and understand without having to be in front of your PC. I am not necessarily a nuby but I did found that because the authors cover the Rails ideas so well it helped me pick up on some of the finer points and nifty tricks that I have been missing while I learnt Rails.

I am sure the authors will address any shortcomings mentioned by the other reveiwers with respect to choice of a pagination strategy etc.. They have already devoted a section on the website to possible improvements to the book's code.

I also have the Alan Bradburne book and I recommend you get them both. They both have their strengths. Get RailsSpace to help you get a really solid foundation and core user interaction site and Rails Social Networking Sites to get you up and running quickly with everything else.

This is a wonderful book to start learning ruby on rails with. It takes you step by step and explains in details the various properties and logic behind obscure looking ruby code. The book teaches you how to use Ruby on Rails by showing what you need to do to construct a social networking website. So at the end of the book, you can actually have a fully functioning webpage. I definitely recommend this book to anyone who wants to learn Ruby on Rails.

A great book to help you understand in more detail about rails projects. I found it very insightful. I was not interested in creating a social networking site per se, but it provide me more information on topics such as authentication/authorization under rails, and maintaining a profile, etc.

I'm not an experienced coder by any means but I do have some very basic fundamental understanding of both Web programming (HTML, PHP, PERL, CSS) and working within Terminal (on my MacOSX). I am on page 45 of this book and I have needed to reference more websites and other documentation to get through the examples then is reasonably acceptable. The book is definitely out of date compared to the current Rails edition and you can read this fact as even written by the author on this very Amazon page. What he doesn't tell you or rather leads you to believe is that you will be able to get past the subtle or relatively easy conflicts of what the book says and of what you actually need to program the RailsSpace application simply. This is just not true. The user group website is very difficult to navigate through and similarly confusing. It is mostly written by users of questionable credentials. Just a few examples of fundamental problems I am having: 1) Installing Ruby and Rails is not really explained. The author breezes through where to download the files and the few command prompts that are needed to make it work but fails to adequately cover where these installations are in your directory and how to change those paths. 2) Just going with what ever is defaulted will mess you up when you have to install MySQL. I can't get my RailsSpace application to talk to MySQL at this point. 3) I have then found out that Rails 2 doesn't use MySQL for default but SQLite so on a totally different site I found that I had to make the railsspace application differently, negating the work that was done already. 4) I then had to install MySQL manually and have no help for the errors I get when trying to run the application. I have wasted so much time and attempted so many things trying to get the components to work together that I am certain I have screwed up my system by trying every suggestion I see on the internet. I don't know how to just scrap it all and start from scratch now knowing what irrelevant information is in the book now and substitute it with the right stuff. On the authors blog site he tells you that they have both abandoned working on the RailsSpace application to pursue other things and leave you in the hands of a Google user group. This is unprofessional and the publisher of the book should pull this dated, now complicated and obviously unsupported version of the book. They should rewrite it according to the current Ruby and Rails version if they want to continue selling it. I am so upset that I have invested the time I did into this book and that I spent the money on it too. I really liked the idea but all that you will do if you buy this book is make more work for yourself. The changes to the Rails program and syntax is not the authors fault but why are they too good to write an update and release it so that it is compatible? Look at all the 4-5 star reviews and note the dates they were written- as I said I'm sure when the book was current it was great but now it is no longer a "step-by-step guide" but a rough outline.

I have gone through this book several times and am still using it actively to learn Ruby on Rails. In my judgment, if you buy this book in conjunction with David Black's book "Ruby for Rails:..", you should be all set. Granted both books are a bit old considering that Rails 2.0.x is out, still nothing comes close in terms of the sheer usefulness from a learning point of view to these two books. I own several other Ruby and Ruby on Rails texts, but these are the two texts that I find myself frequently turning to. Initially, towards the beginning, it was David Black text, now increasingly so, it is this text.
Both Michael and Aurelius are very bright and gifted educators and pretty good developers at the same time.
I would look forward to buy another text by these two authors which takes off where this text leaves us and has been updated for Rails 2.0.x. Go for it gentlemen, I am cheering for you.

My own website is entirely hand-coded, soup to nuts. That has advantages (I get to control things entirely) and disadvantages (I have reinvented more than one wheel). I have looked at all kinds of content management systems like Drupal and so on, but have just never been ready to give up control.

It looks like Ruby on Rails just might convince me to do it. It seems to me that ROR has the right mix of freedom and ease of use, so I have been poking around here and there reading about it.

I had received this book a month or two back but accidentally buried it under a bunch of other stuff and it just surfaced this week. Good timing, because this was the week I had decided to start diving into ROR a bit deeper, and I found this very helpful in getting started.

"RailSpace" is a tutorial that leads you through building an imaginary application with ROR. I followed it on my Mac OS X Leopard, where the only difference is that Leopard uses Sqlite3 instead of MySQL as its default database. For everything but the raw database examples, it makes absolutely no difference, but you certainly can install MySQL if you want. Just to convince myself that Ruby really doesn't care I did that, and did one project with MySQL and one with the default Sqlite3 - it really makes no difference.

I liked that "RailSpace" builds its application slowly, modifying it as the chapters go along. That's an excellent way to teach, because in the real world we constantly modify our websites, adding new features, restructuring, redesigning: you might as well learn how to do that in ROR from day one, and this book takes exactly that approach.


I also liked that the authors paid attention to both looks and ease of use without clouding things up with too much detail. The project design is simple, but with enough attention paid to presentation to understand how to accomplish that in your "real" projects, and the same is true for niceties like data validation: the authors do enough to show the concepts without burying us in it.

They also included deliberate mistakes - that is, small problems which you might notice before they get around to pointing them out. That's good, because often the best way to understand WHY you need to do something this way is to see what happens when you don't.

All in all, I found this very helpful and well done.

Excellent book that shows you, step by step, how to write a commercial quality website.

Before buying this book I'd worked through several on-line Rails tutorials. I'd bought a couple Rails books. But I didn't know how to write production quality Rails suitable for a real commercial application.

This book bridges the gap. RailsSpace explains the how and the *why* in the right amount of detail. The *why* is what really shows you how Rails is meant to work.

Some examples:
- HTML with cascading style sheets right from the beginning.
- Rails test capabilities early on.
- The right way to use (and understand) model-controller-view.
- Database sessions (for reasonable performance).
- Debugging.
- Using the Rails console.

In addition, the writing is clear, the step-by-step organization is fast and easy to follow, and the examples are excellent.