Somebody suggested SmallCap and that sounds great. This is by no stretch
of the imagination Capistrano, so it might better be named MicroCap but
it may be useful to some who have (as I do) modest needs in this regard,
especially for on-server versioning.
Here’s a preview of the usage:
Usage: ruby smallcap.rb [options]
-s, --server=SERVER Copies app to specified server.
Default: yourserver.com
-u, --user=USER User id for server.
Default: youruserid
-d, --deploy-path=FULLPATHNAME Specifies the full path on server
for deployment.
Default:
/full/path/to/deployment/directory
-e, --edge_rails If present, copies edge or gem
rails to server.
-p, --plugins If present, copies plugins
directory to server.
-c, --components If present, copies components
directory to server.
-i, --script If present, copies script directory
to server. USE WITH CAUTION
-g, --config If present, copies config directory
to server. USE WITH CAUTION
-t, --temp-dir=TMP_DIR If present, sets the temp directory
for caching the files prior to
prop. Note that the root
directories must exist.
Default: System temp directory
-f=CONFIG_FILE Specifies the optional
configuration file for deployment.
–configuration-file Default: deploy.yml
-h, --help Show this help message.
SmallCap defaults to loading a deploy.yml file that specifies your
server config, so you don’t have to type all this junk each time.
Additionally, you can have deploy_dev.yml and deploy_test.yml and select
using -f. Finally, SmallCap loads recipe files in the ./recipes
directory. I’m still working on the semantics of this, but it’s where
you will do the pre-deployment stuff.
I’m not ready to put this out ITW yet because it’s not ready for prime
time, but…comments on what you see? Useful? Not?
