Generating access_key_id and secret_access_key for S3.yml

A very newbie question about the the access_key_id and secret_access_key for the S3.yml config file - are these keys something I make up on my own or are they keys that I should use some auto-generator of some kind to create them. Sorry if I missed the specifics about generating these keys in the

Re: Generating access_key_id and secret_access_key for S3.yml

These are the keys that Amazon give you in order to connect to S3 - they are only available from your amazon login, and are private to you. Neil On Thu, Aug 26, 2010 at 5:23 PM, Dennis dennismaj...@gmail.com wrote: A very newbie question about the the access_key_id and secret_access_key for

Re: free vs. paid heroku app performance

Can't you set something up to request a page on the app every so often to simulate traffic? I ran into the same issue on Google App Engine and did this to prevent the resources behind my app to not wind down. On Thu, Aug 26, 2010 at 2:32 PM, Eric Anderson e...@pixelwareinc.comwrote: On

Using resque-scheduler

We're trying to use resque-scheduler with Heroku, but resque-scheduler requires two processes to be running, corresponding to the tasks resque:scheduler (which schedules jobs), and resque:work (which pops jobs off the queue and performs the work). Given that workers on Heroku only run the

‘No route matches’ with paperclip and S3 on Hero ku

Setting up paperclip to use S3 on my local dev system was a snap. However, I am not able to get it to work on Heroku. The file uploads successfully: [paperclip] Saving attachments. [paperclip] saving photos/2/small.jpg [paperclip] saving photos/2/original.jpg However, views that try to link

Undefined method error

I have bundler 1.0 running on rails 2.8. After this, I am getting a weird problem. All webpages have started giving me Undefined Method error. Log does not suggest anything either. Please refer to the log below and suggest me if you have encountered similar problem before. thank you. Error

Re: Backup for MongoHQ Data

Not sure what that error message means, sorry. You might ask in the MongoDB google group - 10gen is good about helping users with issues: http://groups.google.com/group/mongodb-user Also, I should have mentioned before that there's a guide to mongorestore and the other MongoDB import/export

Re: Backup for MongoHQ Data

I use a mongoexport mongoexport -h [host]:[port] -d [database] -u [user] -p [password] -c [collection] -o [path, e.g. ~/tmp/mongoexport/export.json] And a mongoimport mongoimport -h [host]:[port] -d [database] -u [user] -p [password] -c [collection] --file [file, e.g.

Re: Backup for MongoHQ Data

And the answer is: To restore the dump to your local instance of Mongo, make sure you're in the original directory (the one with subdirectory 'dump') and type mongorestore I was trying too hard, I guess. : ) Hemal's suggestion of mongoexport makes a nice readable JSON file for one collection

Re: ANNOUNCEMENT: Upgrading to Bundler 1.0.0.rc.6

Due to some complications, we're pushing this deploy to Monday. Thanks, Terence On Tue, 2010-08-24 at 18:16 -0500, Terence Lee wrote: Hello, Bundler 1.0.0.rc.6 was pushed out yesterday with some bug fixes. You can view the complete changelog here:

model missing required attr_accessor for 'photo_file_name' when uploading with paperclip and S3 on heroku

Setting up paperclip with S3 in my linux dev environment was a snap -- everything works out of the box. However, I can't get it to work on Heroku. When I try to do an upload, the log shows: Processing ItemsController#create (for 72.177.97.9 at 2010-08-26 16:35:14) [POST] Parameters:

Re: model missing required attr_accessor for 'photo_file_name' when uploading with paperclip and S3 on heroku

One thought: Have you migrated your DB? heroku rake db:migrate heroku restart -Kelly On Aug 26, 2010, at 7:57 PM, eksatx wrote: Setting up paperclip with S3 in my linux dev environment was a snap -- everything works out of the box. However, I can't get it to work on Heroku. When I try to

Re: model missing required attr_accessor for 'photo_file_name' when uploading with paperclip and S3 on heroku

That was it! I actually had done: heroku rake db:schema:load Shouldn't that have accomplished the same thing? Maybe something went wrong during that process, although it did not return any errors. At any rate, doing heroku rake db:migrate and heroku restart solved the problem. Thanks! On Aug