• Keep it in one file
• Small Apps, Many Mounts
• Give Us a `create’ Method
• The Camping Server

Keep it in one file

Keep it in one file

Generally, the idea is keep your app small and store in a single file. Your app will end up with four sections:

1. Camping setup

ruby do
  require 'rubygems'
  require 'camping'
  Camping.goes :Blog
end

2. Models

ruby do
  module Blog::Models
    class User < Base; end
    class Post < Base; belongs_to :user end
  end
end

3. Controllers

ruby do
  module Blog::Controllers
    class Index < R '/'
      def get; render :index end
    end
  end
end

4. Views

ruby do
  module Blog::Views
    def layout
      html { body { self << yield } }
    end
    def index
      div.page "Welcome!"
    end
  end
end

(Optional) You may choose to Give Us a `create’ Method.

What if Things Get Out of Hand?

What if Things Get Out of Hand?

If you’re piling up models and controllers, your file may begin to exceed 200 lines, which means lots of paging up and down. Go ahead and store your models, controllers and views in three separate files. Your directory structure should end up like this:

blog.rb
blog/
  models.rb
  controllers.rb
  views.rb

(Note, for the development reloading to work, your required files (models.rb etc.) must be in a subdirectory named after your app.)

Your blog.rb would still contain the setup (No. 1):

ruby do
  require 'rubygems'
  require 'camping'
  Camping.goes :Blog
  require 'blog/helpers'  # if needed
  require 'blog/models'
  require 'blog/views'
  require 'blog/controllers'
end

Small Apps, Many Mounts

Small Apps, Many Mounts

Rather than building huge Camping apps, the idea here is to write small apps which can each be mounted at directories on your web server. One restriction: these apps will share a database. However, this allows applications to access each other’s tables and simplifies setup and configuration.

The camping tool starts a web server which mounts apps in this fashion. If you want to mount all your apps, run camping apps/**/*.rb.

You’ll end up with:

• http://localhost:3301/blog, a blogging app.
• http://localhost:3301/tepee, a wiki app.
• http://localhost:3301/charts, a charting app.

In your app, if you’re using the R() method to build your links, Camping will make sure the mount is added properly to links.

For example, if R(View, 1) is used in the blogging app mounted at /blog, the link will be written as /blog/view/1. If later you mount the blog at /articles instead, Camping will write the link as /articles/view/1.

Give Us a `create’ Method

Give Us a `create’ Method

ruby do
  def Blog.create
    # Code in here will run when the app starts, or reloads, but not when requests happen.
    # You can use it to create database bits and pieces, files, folders, and so on.
  end
end

The Camping Server

The Camping Server

The Camping Server is basically a set of rules. At the very least, The Camping Server must:

• Load all Camping apps in a directory.
• Load new apps that appear in that directory.
• Mount those apps according to their filename. (e.g. blog.rb is mounted at /blog.)
• Run each app’s create method upon startup.
• Reload the app if its modification time changes.
• Reload the app if it requires any files under the same directory and one of their modification times changes.
• Support the X-Sendfile header.

bin/camping

bin/camping

Camping comes with a very simple version of The Camping Server. bin/camping uses either WEBrick or Mongrel (if you have it installed.)

Run it like this: camping /var/www/camping/*. It will follow all of the rules above.

Edit