Skip to content
No description or website provided.
Ruby CoffeeScript JavaScript
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

Pusher Demo

This is a small demo application, that will show how quickly and easily you can integrate Pusher into your web application.

The application is a simple messaging app, where users can register and send messages to other users. We will add Pusher integration in 3 levels:

  • Add realtime update of the hero-unit on the front page, showing how many messages the users have sent to date.
  • Add realtime update of the label showing a logged in user how many unread messages he has.
  • Add a realtime notification for users when they receive a new message.

The project is separated into two different branches:

  • master: This is the application before Pusher has been integrated. It will be our starting point.
  • finished_pusher_integration: This branch contains the finished application with Pusher integration. If you compare this branch to master, you can see each step towards pusher integration as a commit.

In the following sections, I will desribe how I integrated Pusher in this app.

First things first

The first thing you'll want to do, is to log onto and sign up for a free account. From there you also need to setup a new application in the Pusher dashboard and get the API-keys for the app.

You should store thise keys in the environment. I'm using pow as a development server, so I've created a .powrc file in the root of the project with the following content:


1. Install Pusher

To install Pusher, simply add the pusher gem to your Gemfile and do a bundle install

gem 'pusher'

Next we'll want to create an initializer to let Pusher know about the API-keys.

In config/initializers/pusher.rb

Pusher.app_id = ENV['PUSHER_APP_ID']
Pusher.key    = ENV['PUSHER_KEY']
Pusher.secret = ENV['PUSHER_SECRET']

Finally we need to include the Pusher Javascript client.

In app/views/layouts/application.html.erb

  <%= javascript_include_tag "", "application" %>

See the commit for this step

2. Make Pusher App Key available to client side

Since the client side also needs to talk to Pusher, we also need to make the Application Key available to the client side.

In app/views/layouts/application.html.erb

  <script type="text/javascript">
    window.pusher_key = '<%= ENV['PUSHER_KEY'] %>';

See the commit for this step

3. Initialize Pusher on client side and connect to public channel

Next up we'll initialize Pusher in our javascript and connect to a public channel.

Pusher has 3 kinds of channels:

  • Public: These channels are, as you might think, public which means that anyone can listen in on what happens there.
  • Private: These channels are private and only authorizes users can connect to these channelse.
  • Pressence: These special channels are used to track who's online. This type of channel will not be covered here, but check out Pushers official documentation for more info.

In app/assets/javascripts/application.js

window.pusher = new Pusher(window.pusher_key);
window.broadcast_channel = pusher.subscribe('broadcast');

Note that I store the pusher and broadcast_channel in window - which is to make it available to our coffeescript in the later steps.

See the commit for this step

4. Push "Total Messages Sent"

The first thing that we'll add realtime functionality to, is the hero-unit on the front page, that shows how many messages our users have sent to date.

For this purpose I've prepared an Observer to observe when new Message-models have been created. We will use this observer to push an event to our connected clients, when a message is created.

In app/models/message_observer.rb

def after_create(message)
  Pusher['broadcast'].trigger!('total_messages_changed', {:value => pluralize(Message.count, 'message', 'messages')})

Notice the syntax of the Pusher gem:


We defined our channel-name in the previous step to broadcast and here we define the name of the event to total_messages_changed

Note that just sending a count of total messages is a naive approach, since it can result in race conditions. But it will suffice for demonstration purposes.

Next we'll want to listen for this event on the client side.

In app/assets/javascripts/

$ ->
  window.broadcast_channel.bind 'total_messages_changed', (event) ->

Also notice the syntax of the Pusher Javascript SDK:


Every key that you set in the data-hash on the server will be available as a property in the event-object that is passed to the event-handler.

The hero-unit on the front page now updates automatically every time a new message is sent.

See the commit for this step

5. Uncomment PusherController#auth

We now want to push the number of unread messages to a user, when he receives new messages, but to do this we're going to need to use private channels, because we don't want our users to know each others number of unread messages.

The way Pusher has implemented private channels is that when a client tries to connect to a private channel, the Pusher Javascript SDK will perform a POST request to your app with information about the channel that he is trying to connect to, and unique socket id. It is then up to us to determine if the user is authorized to connect to this channel.

If the user is authorized, we need to call the Pusher API with the unique socket id. This will return a key that we should pass on to the client. The client will then use this key to finish connecting to the channel.

By default Pusher will make the POST request to /pusher/auth

I've already prepared a controller to handle this, so simply uncomment the content of the auth-action in PusherController:

if current_user && params[:channel_name] == "private-user_#{}"
  render :json => Pusher[params[:channel_name]].authenticate(params[:socket_id])
  render :text => "Not authorized", :status => '403'

See the commit for this step

6. Make the id of the current user available to the client side

Every channel that has a name that starts with private- will be a private channel.

We're going to name our private channels: private-user_ID_OF_USER.

Example: private-user_42

So for the client side to be able to know what channel to connect to, we need to expose the id of the current user.

In app/views/layouts/application.html.erb

  <script type="text/javascript">
    <%= "window.user_id = #{};" if current_user %>

See the commit for this step

7. Subscribe to private channel

We can now connect to the private channel, if a user is logged in.

In app/assets/javascripts/application.js

if (window.user_id)
  window.private_channel = pusher.subscribe('private-user_' + window.user_id);

See the commit for this step

8. Push "Unread Messages Count"

Now we can use this private channel to send the number of unread messages to a user, when he receives a new message.

In app/models/message_observer.rb

def after_create(message)
  Pusher["private-user_#{}"].trigger('unread_messages_changed', {:value => message.recipient.received_messages.unread.count})

And we can listen for this event on the client side.

In app/assets/javascripts/

if window.private_channel
  window.private_channel.bind 'unread_messages_changed', (event) ->

See the commit for this step

9. Push "New Message Notification"

Finally we are going to push a notification to users, when they receive a new message, with an excerpt of the message and a link to read the message.

For this we're going to use the Gritter jQuery Plugin, which have already been prepared in the application.

In app/models/message_observer.rb

def after_create(message)
  Pusher["private-user_#{}"].trigger('new_message', {
    :sender => message.sender.username,
    :subject => message.subject,
    :excerpt => truncate(message.body, :length => 150),
    :url => "/messages/#{}"

In app/assets/javascripts/

if window.private_channel
  window.private_channel.bind 'new_message', (event) ->
      title: "You've received a new message from " + event.sender
      text: '<blockquote>' + event.excerpt + '</blockquote><a href="' + event.url + '" class="btn success small">Read</a>'
      sticky: true

See the commit for this step


This concludes the demo and I hope you now have a clear picture of how easy it is to integrate Pusher into a Rails application.

Please feel free to message me if you have any questions.

Oh, and you can use the source-code for this demo application in any way you like, but attribution is always greatly appreciated! :)

Something went wrong with that request. Please try again.