Thanks! That's probably why most Rails deployment texts don't mention this. sqlite might not be the most common choice for production.
/PEZ On May 3, 9:12 pm, "Rafael G." <[email protected]> wrote: > If your database is in a file(as SQLite do) you should put it in > shared_path, then implement a task that "relink" every time you do a > deploy. > Example: > > after "deploy:symlink", "deploy:symlink_mailer" > > desc "Make symlink for mailer.rb" > task :symlink_mailer_rb , :roles => :app do > run "ln -nfs #{shared_path}/config/mailer.rb > #{current_path}/config/initializers/mailer.rb" > end > > Regards > > > > > > PEZ wrote: > > Appologies in advance if this is an RTFM. I have tried to figure it > > out on my own, even bought that Deploying Rails Application and read > > it. There's something I'm missing. > > > The problem. When I deploy, then a new release directory is created. > > All with new code and such. Excellent. The problem is that the > > production database isn't present in this new release directory. Thus > > the application doesn't work after a deploy. What am I missing? > > > Thanks in advance, > > /PEZ > > -- > Rafa --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
