ok so the log file error is due to the log file not existing in my shared directory - not sure how to address it but probably not a show stopper
the extension errors appear to be due to me not using Git properly? I found a thread that discusses having to use Git submodules to manage extensions .. going to play with that and see what happens :P On Fri, Dec 17, 2010 at 10:57 AM, Fima Leshinsky <flesh...@gmail.com> wrote: > hm .. so I got the database.yml symlink in place but now there's this. any > ideas how to debug it? the user that I'm connecting to the server with owns > all of the application tree so I'm not sure why it's complaining about > access to the log file. any ideas where to even begin? > > * executing "cd /var/www/html/radiant/releases/20101217185342; rake > RAILS_ENV=production db:migrate" > servers: ["172.116.1.12"] > [172.116.1.12] executing command > ** [out :: 172.116.1.12] (in > /var/www/html/radiant/releases/20101217185342) > ** [out :: 172.116.1.12] Rails Error: Unable to access log file. Please > ensure that /var/www/html/radiant/releases/20101217185342/log/production.log > exists and is chmod 0666. The log level has been raised to WARN and the > output directed to STDERR until the problem is fixed. > ** [out :: 172.116.1.12] Could not load extension from file: > capistrano_extension. > ** [out :: 172.116.1.12] #<NameError: uninitialized constant > CapistranoExtension> > ** [out :: 172.116.1.12] Could not load extension from file: > code_ray_extension. > ** [out :: 172.116.1.12] #<NameError: uninitialized constant > CodeRayExtension> > command finished > > >
