On 26.04.2009, at 20:51, Abhi wrote: > Hi all, > > I'm currently new to capistrano. After trying out various solutions > built in PHP - I found capistrano the best one. I'm using it to > automate a simple build process used by our team from a last few days. > > Here's the process: > > 1. Create a new directory called 'app' in directory as specified in > ":repository" variable. > 2. Checkout at this 'app' directory. > 3. After checkout, read a file called CAKE, which contains the rev. > number of CakePHP framework to be used. > 4. Depending on revision, copy it from another library directory (from > same server) > 5. Perform basic MySQL stuff > 6. Create sub-domain like: someApp.mydomain.com > 7. This subdomain should automatically point out to /current directory > > Because I'm not a ruby player yet - I'm not sure how easy/hard it will > be to do with Capistrano. Please let me know what you guys think? > Do you want to run all that stuff remotely? Capistrano is more of a "check out this code and do stuff with it" tool. What you describe sounds to me more like a job for writing a plain Rakefile (which you can then easily call remotely with Capistrano) for use with Ruby's build tool rake. In a Rakefile you can include libraries to e.g. talk to MySQL, and you can use Ruby's built-in file system support. I think this kind of script to run these administrative commands is more fitting.
I think you'd be better off this way, since writing it in plain Capistrano run commands (calling shell commands in turn) would result in a pretty awkward code. Cheers, Mathias -- http://paperplanes.de http://twitter.com/roidrage --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
