For a non-rails project, be sure to override the deploy:finalize_update task, so that it doesn't do anything:
deploy.task :finalize_update do end That task contains most of the rails-specific deployment behavior. - Jamis On Jun 5, 2007, at 6:18 AM, Valentino Volonghi wrote: > > Hi all, I'm trying out capistrano 2 for my own non-rails projects. > > I currently have a preferred application layout that can be outlined > in the following > way. > At the root there are 6 directories: > > - configuration: contains the configuration 'framework' and the > default > config file. > > - database: contains all the SQL files > > - logs: contains all the log files that the application generates, by > default web.log is created there (and it is also the only log file > created currently) > - application_name: contains the actual application and it has the > following > subdirectories: > > - storage: contains the database modules > - web: contains the web stuff > > > - static: contains the static part of the website and has 3 > subdirectories > each for a specific use: s is for styles, i for images and j for > javascript, it's mapped at the url: /static/ > > - template: contains all the templates for the application. > > > Today I tried running cap deploy:update but it failed because some > symlinks > failed to be created. > > How do I need to set up my own application to avoid problems with > capistrano? > I know that some default recipes are strictly for rails, but still I > wouldn't mind using > some of the basic ones for the job. > > thanks. > > -- > Valentino Volonghi aka Dialtone > Now running MacOS X 10.4 > TechBlog: http://vvolonghi.blogspot.com > Home Page: http://www.twisted.it > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
