Browse files

Update readme; release 0.5.3.

  • Loading branch information...
1 parent 7ccee04 commit 45db0b43034a6dfc2e806bd0c515e9076a45555f @technomancy committed Apr 21, 2009
Showing with 17 additions and 4 deletions.
  1. +5 −0 History.txt
  2. +11 −3 README.rdoc
  3. +1 −1 lib/harker.rb
View
5 History.txt
@@ -1,3 +1,8 @@
+=== 0.5.3 / 2009-04-21
+
+* Load app extensions on a per-instance basis.
+* Depend on hoe so Rails' test task isn't interfered with.
+
=== 0.5.2 / 2009-03-31
* Remove Hoe test task if supported.
View
14 README.rdoc
@@ -44,8 +44,8 @@ instance:
$ your_app init ~/apps/your_app_3001
-Then edit /var/myapp/database.yml with your database settings. At that
-point you should be able to bring up your database:
+Then edit ~/apps/your_app_3001/database.yml with your database
+settings. At that point you should be able to bring up your database:
$ your_app migrate ~/apps/your_app_3001
@@ -67,7 +67,15 @@ If you omit the second argument, it defaults to the current directory.
For deployment, simply publish your gem to a gem server (public or
private), install it on the target server, and launch it via the bin
-wrapper.
+wrapper as shown above.
+
+== Extensions
+
+Sometimes it becomes necessary to hot-patch a deployed app. Instead of
+editing the code inside your gem home, (which is Fraught with Peril)
+you can place .rb files inside your instance directory's extensions/
+directory. These will be loaded immediately after the application is
+required.
== Requirements
View
2 lib/harker.rb
@@ -6,7 +6,7 @@
# rather than by Harker itself.
#
module Harker
- VERSION = '0.5.2'
+ VERSION = '0.5.3'
ACTIONS = %w(start stop restart init migrate console)
GEM_ROOT = Gem.loaded_specs[File.basename($0)].full_gem_path rescue '.'

0 comments on commit 45db0b4

Please sign in to comment.