Just in case people read this later on and have forgotten, right now S3 has a 5 GB file size limit, so if your database backup tar is larger than that you might run into problems.
Carl On Wed, Mar 24, 2010 at 9:19 AM, Matt Buck <mattb...@capitalthought.com>wrote: > That's correct. I use this functionality to automate the process of > backing up my database to S3. Eventually, I'd like to roll in Jesse's work > on the gist into the backup plugin so that I am only throwing the db dump > onto S3, rather than the code/dump bundle. > > - Matt Buck > > On Tue, Mar 23, 2010 at 4:43 PM, Mike <mikel...@gmail.com> wrote: > >> What exactly can you do with the bundle after you've backed it up? As >> far as I can tell, and Heroku support told me the same thing, there's >> no way to directly use your bundle on Heroku again once you've taken >> it off. >> >> On Mar 23, 4:01 pm, Matt Buck <mattb...@capitalthought.com> wrote: >> > 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 <hon...@gmail.com> 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 <r3ap3r2...@gmail.com> 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 her...@googlegroups.com. >> > > To unsubscribe from this group, send email to >> > > heroku+unsubscr...@googlegroups.com<heroku%2bunsubscr...@googlegroups.com> >> <heroku%2bunsubscr...@googlegroups.com<heroku%252bunsubscr...@googlegroups.com> >> > >> > > . >> > > 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 her...@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscr...@googlegroups.com<heroku%2bunsubscr...@googlegroups.com> >> . >> 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 her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com<heroku%2bunsubscr...@googlegroups.com> > . > 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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
