Thanks for the shout-out, Jesse.  I actually recently pluginized the code
from that bundle backup gist, so anyone can have access to that
functionality with a simple:

heroku plugins:install backup

(The above command will only work if you have
herocutter<http://herocutter.heroku.com>installed - which you
definitely should.)

That gives you access to the following command:

heroku backup

This will destroy the most recent bundle, capture a new one, download it,
and then push it up to S3.  If you're already using paperclip in a Rails
project, this should work for you out of the box.

- Matt Buck

On Tue, Mar 23, 2010 at 10:51 AM, Terence Lee <[email protected]> wrote:

> Like people have said.  Taps doesn't support foreign keys, so if you
> aren't pulling/pushing then you'll have foreign key support.  Use the
> bundle and get the code dump and postgresql  dump.  Also, you can open a
> support ticket to get a pgdump as well.  The only thing really missing
> is push support with foreign keys.
>
> The target audience is hosting any ruby application where you don't want
> to manage your own infrastructure.
>
> Terence
>
> On Tue, 2010-03-23 at 03:41 -0700, Alex wrote:
> > I mirror both of those points, proper dumps to S3 are stopping me
> > putting 2 sites on Heroku at the moment.
> >
> >
> > Alex
> >
> > On Mar 23, 6:16 am, Chris <[email protected]> wrote:
> > > I just did a heroku db:pull and was VERY bummed to find that all my
> > > foreign key constraints were lost.  Luckily I haven't launched the
> > > site yet.  Referential data integrity is a major concern, and
> > > obviously my foreign keys are not being implemented on the heroku
> > > database.
> > >
> > > Question:
> > > What is the recommended way for dealing with foreign key constraints
> > > in Heroku if they get lost doing a db:push?
> > >
> > > Side Note:  The database interaction is currently the #1 issue why I'm
> > > considering NOT using Heroku.  I can deal with the read only
> > > filesystem, but what's the point in using Postgresql if you aren't
> > > going to preserve foreign key constraints?  For the little user blog
> > > it probably doesn't matter much, but for any of us that are
> > > considering spending a bunch of money on dynos and dedicated databases
> > > this is a major shortcoming.
> > >
> > > Features that I would consider a must for any realistic business site:
> > > 1) The ability to TRULY dump the database.  (pg_dump) Preferably to
> > > S3.  And of course the reverse (importing the database).
> > > 2) Access to the database through the console (psql).  I realize that
> > > I can access it through the models, this isn't what I want, I want to
> > > be able to login to the console and issue custom sql queries.
> > >
> > > My $0.02
> > >
> > > So out of curiosity, as a business, who is Heroku's target audience?
> > >
> > > -Chris
> >
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Heroku" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<heroku%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to