Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

An example Rails 3 app with subdomains and authentication (using Devise). With a tutorial.

branch: master
README.textile

Rails3-Subdomain-Devise

Use this project as a starting point for a Rails 3 application that uses subdomains and authentication. User management and authentication is implemented using Devise.

Is the app useful to you? Follow me on Twitter:
http://twitter.com/danielkehoe
and tweet some praise. I’d love to know you were helped out by what I’ve put together.

Any issues? Please create an Issue on GitHub.

“Building It” Tutorial

A complete walkthrough tutorial is available on the GitHub wiki:

View the Tutorial

The tutorial documents each step that you must follow to create this application. Every step is documented concisely, so a complete beginner can create this application without any additional knowledge. However, no explanation is offered for any of the steps, so if you are a beginner, you’re advised to look for an introduction to Rails elsewhere. Refer to the Rails Guides site for help if you are a beginner.

For an introduction to Rails 3 and subdomains, see Ryan Bates’s screencast Subdomains in Rails 3 (a transcription is available from ASCIIcasts).

If you simply wish to modify the application for your own project, you can download the application and set it up as described below, without following the tutorial.

Use Cases

What Is Implemented

This example implements “blog-style subdomains in Rails.” The example is similar to the application shown in Ryan Bates’s screencast Subdomains in Rails 3 but adds authentication using Devise. In this example, there is a “main” domain where anyone can visit and create a user account. And registered users can create any number of subdomains which could host blogs or other types of sites.

What Is Not Implemented

Another use of subdomains is often called “Basecamp-style subdomains in Rails.” Visitors to the main site can create a user account which is then hosted at a subdomain that matches their user name. Each user has only one subdomain and when they log in, all their activity is confined to their subdomain. A user’s home page and account info is accessed only through the subdomain that matches their user name. For an example of “Basecamp-style subdomains in Rails,” see:

Steve Alex’s Basecamp-style fork.

(Got your own? Contact me and I will add it here.)

No testing (RSpec or otherwise) is implemented. This app only serves to demonstrate Devise working with subdomains on Rails 3.

Assumptions

This tutorial is based on Rails 3 and Devise 1.1.3.

Before beginning this tutorial, you need to install

  • The Ruby language (version 1.8.7 or 1.9.2)
  • Rails (version 3.0.0)
  • A working installation of SQLite (preferred), MySQL, or PostgreSQL

I recommend installing rvm, the Ruby Version Manager, to manage multiple versions of Rails if you have a mix of Rails 3 and Rails 2 applications.

If you are using rvm, you can see a list of the Ruby versions currently installed:
$ rvm list

Check that appropriate versions of Ruby and Rails are installed in your development environment:
$ ruby -v
$ rails -v

If you intend to deploy to Heroku, note that Heroku supports Ruby version 1.8.7 but not Ruby version 1.9.2 (as of 5 September 2010).

Generating the Application

To get started with a new Rails application based on this example, you can generate a new Rails app:

$ rails new app_name -m http://github.com/fortuity/rails3-subdomain-devise/raw/master/template.rb

This creates a new Rails app (with the app_name you provide) on your computer. It includes everything in the example app (as described in the tutorial).

Plus, the application generator template offers you the following options:

  • set up your view files using the Haml templating language
  • use jQuery instead of Prototype
  • install the heroku gem for deployment to Heroku
  • use Mongoid instead of Active Record for database access

If you wish to “change the recipe” to generate the app with your own customized options, you can copy and edit the file template.rb.

Downloading the Example

I recommend “Generating the Application” as described above. If that doesn’t work, or you simply wish to examine the example code, you can download the app (“clone the repository”) with the command

$ git clone git(at)github.com:fortuity/rails3-subdomain-devise.git

The source code is managed with Git (a version control system) and hosted at GitHub. You’ll need Git on your machine (install it from http://git-scm.com/).

Set Up Gems

About Required Gems

The application uses the following gems:

  • rails (version 3.0.0)
  • sqlite3-ruby
  • devise (version 1.1.3)
  • friendly_id (version 3.1.7)

I recommend checking for newer versions of these gems before proceeding:

The app has been tested with the indicated versions. If you are able to build the app with a newer gem, please create an issue on GitHub and I will update the app.

Install the Gems

Install the required gems on your computer:

$ bundle install

If you need to troubleshoot, you can check which gems are installed on your computer with:

$ gem list --local

Getting Started

Configure Email

Configure email by modifying

config/initializers/devise.rb

and setting the return email address for emails sent from the application.

You may need to set values for your mailhost in

config/environments/development.rb
config/environments/production.rb

Set Up Configuration for Devise

This app uses Devise for user management and authentication. Devise is at http://github.com/plataformatec/devise.

You can modify the configuration file for Devise if you want to use something other than the defaults:

config/initializers/devise.rb

Set Up the Database

Create a Database and Run Migrations

Create an empty database. You can do this by running a rake command:

$ rake db:create

Run the migrations:

$ rake db:migrate

You can take a look at the database schema that’s been created for you:

db/schema.rb

Seed the Database With Users and Subdomains

You’ll want to set up a default user so you can easily log in to test the app. You can modify the file db/seeds.rb for your own name, email and password:

puts 'SETTING UP EXAMPLE USERS'
user1 = User.create! :name => 'First User', :email => 'user@test.com', :password => 'please', :password_confirmation => 'please'
puts 'New user created: ' << user1.name
user2 = User.create! :name => 'Other User', :email => 'otheruser@test.com', :password => 'please', :password_confirmation => 'please'
puts 'New user created: ' << user2.name
puts 'SETTING UP EXAMPLE SUBDOMAINS'
subdomain1 = Subdomain.create! :name => 'foo'
puts 'Created subdomain: ' << subdomain1.name
subdomain2 = Subdomain.create! :name => 'bar'
puts 'Created subdomain: ' << subdomain2.name
user1.subdomains << subdomain1
user1.save
user2.subdomains << subdomain2
user2.save

Run the rake task to seed the database:

$ rake db:seed

Test the App

You can check that your app runs properly by entering the command

$ rails server (or, abbreviated: $ rails s)

If you launch the application, it will be running at http://localhost:3000/ or http://0.0.0.0:3000/. However, unless you’ve made some configuration changes to your computer, you won’t be able to resolve an address that uses a subdomain, such as http://foo.localhost:3000/. There are several complex solutions to this problem. You could set up your own domain name server on your localhost and create an A entry to catch all subdomains. You could modify your /etc/hosts file (but it won’t accommodate dynamically created subdomains). You can create a proxy auto-config file and set it up as the proxy in your web browser preferences. There’s a far simpler solution that does not require reconfiguring your computer or web browser preferences. The developer Levi Cook registered a domain, lvh.me (short for: local virtual host me), that resolves to the localhost IP address 127.0.0.1 and supports wildcards (accommodating dynamically created subdomains). See Tim Pope’s blog post for a NSFW alternative.

To test the application, visit http://lvh.me:3000/. You can also try http://foo.lvh.me:3000/ or http://bar.lvh.me:3000/.

To sign in as the default user, (unless you’ve changed it) use

  • email: user@test.com
  • password: please

You should delete or change the pre-configured logins before you deploy your application.

Deploying to Heroku

Set Up Heroku

For your convenience, here are instructions for deploying your app to Heroku. Heroku provides low cost, easily configured Rails application hosting.

To deploy this app to Heroku, you must have a Heroku account. If you need to obtain one, visit http://heroku.com/ to set up an account.

Note that Heroku supports Ruby version 1.8.7 but not Ruby version 1.9.2 (as of 5 September 2010). If you’ve developed the app locally using Ruby version 1.9.2, you may wish to use Ruby Version Manager (rvm) to switch to Ruby version 1.8.7 and test the app before deploying to Heroku.

Make sure the Heroku gem is in your Gemfile. If it’s not, add it and run

$ bundle install

to set up your gems again.

If you’ve just created a Heroku account, add your public key immediately after installing the heroku gem so that you can use git to push or clone Heroku app repositories. See http://docs.heroku.com/heroku-command for details.

Create Your Application on Heroku

Use the Heroku create command to create and name your new app> Specify the “bamboo-ree-1.8.7” stack so Heroku will allow you to use Rails 3.

$ heroku create _myapp_ --stack bamboo-ree-1.8.7

Heroku Add-ons and DNS Configuration

You will need the following Heroku add-ons to deploy your app using subdomains with your own custom domain:

  • Custom Domains (free)
  • Custom Domains + Wildcard ($5 per month)
  • Zerigo DNS Tier 1 ($7 per month)

To enable the add-ons, you can use the Heroku web interface or you can enter the following commands:

$ heroku addons:add custom_domains

$ heroku domains:add mydomain.com

$ heroku addons:add wildcard_domains

$ heroku domains:add *.mydomain.com

$ heroku addons:add zerigo_dns:tier1

If you are using the Zerigo DNS service, you will need to set the nameserver with your domain registrar. It can take a few minutes (or longer) for DNS changes to propagate. When DNS is set properly, you should be able to visit mydomain.com or test.mydomain.com in your web browser and see the Heroku default page:

Heroku | Welcome to your new app!

You can check that everything has been added correctly by running:

$ heroku info --app myapp

Set Up Your Application on Heroku

Push your application to Heroku:

$ git push heroku master

Set up your Heroku database:

$ heroku rake db:migrate

Initialize your application database:

$ heroku rake db:seed

Visit Your Site

If you use the heroku command to open your default web browser to your site with

$ heroku open

or if you visit your site with http://myapp.heroku.com/ you’ll see the error, “The page you were looking for doesn’t exist.” That’s because your app is trying to find a subdomain “myapp” that doesn’t exist. You’ll need to visit the site using your own domain name, such as http://mydomain.com/. Domain name service must be set properly to use the Zerigo nameservers.

Troubleshooting

If you get errors, you can troubleshoot by reviewing the log files:

$ heroku logs

Customizing

This application provides no useful functionality apart from demonstrating Devise working with subdomains on Rails 3.

You can use the Site model, controller, and views as a beginning point for customizing the app. For example, you could build a blog application that is displayed on the Site pages.

Devise provides a variety of features for implementing authentication. See the Devise documentation for options.

Issues

Check Issues on GitHub for open issues.

Testing

The application does not include tests (RSpec or otherwise). It relies on Devise which include extensive tests. This application is intended to be a basis for your own customized application and (in most cases) you will be writing your own tests for your required behavior.

Documentation and Support

See the Tutorial for this app for details of how it was built. Please create an Issue on GitHub if you identify any problems or have suggestions for improvements.

You can find documentation for Devise at http://github.com/plataformatec/devise. There is an active Devise mailing list and you can submit Devise issues at GitHub.

This application is provided without additional documentation or support.

Contributing

If you make improvements to this application, please share with others.

  • Fork the project on GitHub.
  • Make your feature addition or bug fix.
  • Commit with Git.
  • Send the author a pull request.

If you add functionality to this application, create an alternative implementation, or build an application that is similar, please contact me and I’ll add a note to the README so that others can find your work.

Similar Applications

For a simple Devise example (without subdomains) for Rails 2.3, see plataformatec/devise_example.

For an example of Devise using subdomains for Rails 2.3, see Subdomain authentication with Rails 2.3.

For a Rails 3 app using Devise and Mongoid (without subdomains), see Rails3 Authentication with Mongoid and Devise.

For an example of “Basecamp-style subdomains in Rails 3,” see Steve Alex’s Basecamp-style fork.

(Got a suggestion? Contact me and I will add it here.)

Credits

Daniel Kehoe (http://danielkehoe.com/) implemented the application and wrote the tutorial.

Is the app useful to you? Follow me on Twitter:
http://twitter.com/danielkehoe
and tweet some praise. I’d love to know you were helped out by what I’ve put together.

Contributors

Thank you to contributor Fred Schoeneman for improving the tutorial.
Thank you to contributor Charlie Ussery for suggesting how to ignore the “www” subdomain.

License

Public Domain Dedication

This work is a compilation and derivation from other previously released works. With the exception of various included works, which may be restricted by other licenses, the author or authors of this code dedicate any and all copyright interest in this code to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this code under copyright law.

Something went wrong with that request. Please try again.