Re: Automating pgbackups

I've got a lot on my plate right now, but I'm not opposed to getting it into a usable state for other people once I get some spare time. On Nov 17, 2:10 am, Trevor Turk trevort...@gmail.com wrote: On Nov 16, 6:44 pm, Andrew C. andrew.c...@gmail.com wrote: I spin up an EC2 instance from my

Getting InvalidAuthenticityToken errors (without changing anything)

All of a sudden, the login form on my site results in InvalidAuthenticityToken exceptions. This happened without changing any code. The same code base is working fine in my staging app. The only difference between production and staging is the use of the New Relic Custom Domain add-ons. I'm

Re: Getting InvalidAuthenticityToken errors (without changing anything)

Ugh. Lesson learned: Don't cache forms. On Aug 31, 10:36 pm, Andrew C. andrew.c...@gmail.com wrote: All of a sudden, the login form on my site results in InvalidAuthenticityToken exceptions.  This happened without changing any code.  The same code base is working fine in my staging app

Caching responses from external APIs

Is there a 'Heroku way' to cache responses from external APIs, like Twitter and Foursquare? I'm using Apigee for Twitter, so the rate limit isn't really an issue, but I need to do something to avoid hitting Foursquare's rate limits. Is it possible to use the existing Varnish instances to cache

Re: Caching responses from external APIs

/memcache http://railsapi.com/doc/rails-v2.3.8/classes/ActionController/Caching... N On Wed, Aug 4, 2010 at 7:45 PM, Andrew C. andrew.c...@gmail.com wrote: Is there a 'Heroku way' to cache responses from external APIs, like Twitter and Foursquare?  I'm using Apigee for Twitter, so

access restrictions for collaborators?

Is there any way to limit what actions can be performed by collaborators? I'd like to be able to, for example, allow a collaborator to pull down code, but not push. Or to pull from the database, but not push. Thanks, Andrew -- You received this message because you are subscribed to the Google

Re: delayed_job for logging

Hi Agustin, I'm definitely interested. Please sign me up. I'll be launching my app with my current home-brew solution; but once it's up, I'll be happy/eager to explore logworm as a better replacement. Thanks! Andrew On Jul 14, 7:16 pm, schapirama schapir...@gmail.com wrote: Hi Andrew,

Re: Programmatically Spinning Workers Up and Down

Hey Pedro, As someone who's still learning uh, Heroku, Rails, Git, Delayed Job . . . how do I go about using this? At the moment I'm using collectiveidea's branch of delayed job, with changes of my own to support Log4r. Should I switch to using your fork of Delayed Job in order to access the

delayed_job for logging

I'm working on a logging solution for my app. After reading various docs, I got the impression that writing my logs to MongoDB in a delayed job would be a good idea. Just one problem: Delayed Job writes to the logs. 1) Creating a Delayed Job writes to the SQL DB, which writes to the logs. 2)

Re: delayed_job for logging

necessary. I've also seen an add-on called LogWorm in the add-ons list I haven't looked into it but would it be of any help to your project? Steve On Jul 13, 9:15 am, Andrew C. andrew.c...@gmail.com wrote: I'm working on a logging solution for my app. After reading various docs, I got