This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 8c91e877b4b8e7cee1af98a90a10398daf9be8f6
tree c0e2ae1c611cef0e4bf817985d77170d0ee788e8
parent 3dc64410aad8509c56f71390beb31941402b96d3
tree c0e2ae1c611cef0e4bf817985d77170d0ee788e8
parent 3dc64410aad8509c56f71390beb31941402b96d3
| name | age | message | |
|---|---|---|---|
| |
README | Sat Mar 01 20:19:25 -0800 2008 | [mdaines] |
| |
Rakefile | Sat Mar 01 20:17:32 -0800 2008 | [mdaines] |
| |
lib/ | Sun Mar 02 14:35:47 -0800 2008 | [mdaines] |
| |
tasks/ | Sun Mar 02 14:35:47 -0800 2008 | [mdaines] |
| |
test/ | Sun Mar 02 14:35:47 -0800 2008 | [mdaines] |
README
BoxingDay
=========
If the public-facing version of your Rails application doesn't have to
involve any scripts and you're the only person using it, BoxingDay can
create a static version of your Rails app, ready for copying to a web
server. A common situation might be a website you maintain yourself on
your computer. It's nice to have Rails' template helpers and a custom
interface for CMSing, but if nobody else is going to see that stuff,
why deploy a whole Rails app?
Just tell BoxingDay what paths to include (I put a file called
boxing_day.rb in the initializers directory) and run
"rake boxing_day:package". For example:
BoxingDay.paths << "/"
BoxingDay.paths << "/products"
Products.find(:all).each { |p| BoxingDay.paths << "/products/#{p.id}" }



