Hello!

Thanks for the replies!

What kind of databases could I use to avoid have to put them under the
shared directory?

Is Postgre good?

Thanks,
David Pham

On Jun 27, 10:43 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
> If you're using sqlite databases in production (not something I'd  
> recommend, actually), then you need to make sure they get put under  
> the shared directory, rather than in your release directory. That's  
> something you'll need to configure in your app, or make happen in some  
> before/after hooks of your own.
>
> - Jamis
>
> On Jun 27, 2008, at 9:14 PM, Anthony Ettinger wrote:
>
>
>
> > On Fri, Jun 27, 2008 at 8:08 PM, BackVerse <[EMAIL PROTECTED]>  
> > wrote:
>
> >> Hello!
>
> >> I just started using Capistrano and on my VPS I ran the following:
>
> >> cap deploy:setup
> >> cap deploy:cold
>
> >> And that setup my application and ran the migrations, so it ran fine.
>
> >> However, now, when I run this command:
>
> >> cap deploy
>
> >> The databases are not being carried over along with their populated
> >> data. All I see in the current release db folder is an empty
> >> production.sqlite3 file and no schema.rb.
>
> >> So I manually have to run rake db:migrate RAILS_ENV=production, and
> >> even that is not what I want since it builds the database anew with  
> >> no
> >> data (I need the previous release's data)
>
> >> Is this normal, or do I need to do something extra to carry over the
> >> database and its data from previous releases?
>
> > If it is a new release (you said you ran setup and cold functions)...
> > Is your DB empty?
> > Are you expecting default data?
>
> > Try adding some things from the application interface (ie:
> > example.com/admin) and then re-deploy...your data should persist.
>
> > --
> > Anthony Ettinger
> > 408-656-2473
> >http://anthony.ettinger.name
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to