Using MongoHQ or Cloudant for Audit Trails
I have a client app that will be coming online soon, and one of the the requirements is that it generates non-repeating serial numbers with no vacancies. There can NEVER, EVER be a repeated serial number. If you are curious, it's financial transactions between countries that are monitored by the FINRA (and others) and they use the serial numbers to detect fraud. So, let's say there is a one-in-a-billion chance that Heroku loses some of my database, no matter how small. They, or we, can restore from backups, but there is no possible way I can determine that records could have been created after the last backup. I'm not so concerned about system downtime, it's potential data loss. As I understand, Heroku does not provide any form of replication for its PostgreSQL offerings (psst, I would be willing to pay $$$). Until then I need to come up with a fault tolerant scheme of data audit trails. First thought - just use Amazon RDS. But whoa, it's really expensive. My clients won't float $3K per month just for data storage. But maybe I'm pricing it wrong and don't understand their pricing model. Second thought - Lotsa backups! Better, but still no guarantee. Third thought - MongoDB or Cloudant. I could use either to write audit logs, essentially duplicating my 'serialized documents', but not the entire db. Since I only need to verify that every new document generated is serialized, seem easy to hit MongoDB/Cloudant to find the last document store and if it does not match the last one in PostgreSQL shut the app down until I can manually restore from the audit log. Seem fairly easy and straightforward. Has anyone else done this? How successful were you? any gotchas? Any gems out there that can do this? Advice appreciated. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@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.
Newrelic config does not work.
Using the instructions for Cedar on: http://devcenter.heroku.com/articles/newrelic Created config/newrelic.yml and copied it from the above page. # newrelic.yml --- <%= ENV["RAILS_ENV"] %>: error_collector: capture_source: true enabled: true ignore_errors: ActionController::RoutingError apdex_t: 0.5 ssl: false monitor_mode: true license_key: <%= ENV["NEW_RELIC_LICENSE_KEY"] %> developer_mode: false app_name: <%= ENV["NEW_RELIC_APPNAME"] %> transaction_tracer: record_sql: obfuscated enabled: true stack_trace_threshold: 0.5 transaction_threshold: apdex_f capture_params: false log_level: info But it results in an error on my development machine: $ rails c syntax error on line 0, col 1: `:' Do I need to copy in the keys manually? or is it that I'm not specifying the ENV["RAILS_ENV"] from the command line? Or, do I just forget creating the newrelic.yml and Cedar will use a default? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@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.
uninitialized constant Rake::DSL
Using Rails 3.0.9 (3.0.7 too), which load rake 0.9.2 with bamboo- mri-1.9.2, causes: $ heroku rake db:migrate rake aborted! uninitialized constant Rake::DSL /app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:8:in `' /app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:6:in `' /app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:3:in `' /app/.bundle/gems/ruby/1.9.1/gems/rdoc-3.6.1/lib/rdoc/task.rb:37:in `' /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks/ documentation.rake:2:in `' /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb: 15:in `block in ' /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb: 6:in `each' /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb: 6:in `' /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/ application.rb:215:in `initialize_tasks' /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/ application.rb:139:in `load_tasks' /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/ application.rb:77:in `method_missing' /app/Rakefile:7:in `' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `load' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `raw_load_rakefile' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2007:in `block in load_rakefile' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2006:in `load_rakefile' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:1991:in `run' /usr/ruby1.9.2/bin/rake:31:in `' (in /app) I had to add, before require 'rake': # Rakefile require 'rake/dsl_definition' But I don't get this on my development machine. Why? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@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.
Running pgbackups:restore no longer works ?
I've just updated to heroku client gem 2.3.0 and I'm trying to transfer the production database to an staging app for testing with: heroku pgbackups:restore `heroku pgbackups:url --app production-app` -- app staging-app This returns (marked with X to omit real app/dump name): ! Could not resolve database http://s3.amazonaws.com/hkpgbackups/appxxx...@heroku.com/b0XX.dump?AWSAccessKeyId=AKIAJYED... (continues with amazon request signature parameterss) ! ! Available databases: ! SHARED_DATABASE (DATABASE_URL) I remember this has worked for me in the past. Am I missing something that's changed recently? Haven't seen any syntax changes for this command in the docs. Any help will be greatly appreciated. Great thanks in advance. Best wishes. -- Estanis. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@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.
Re: New Relic in a Rack app
You can ignore that - it's saying we can't automatically install. You should still be setup with newrelic. Just make sure that your yml file is configured correctly with the ENV var for your key. Oren On Fri, Jun 17, 2011 at 4:12 AM, David Hall wrote: > I have read and followed the steps outlined for Rack apps > in http://devcenter.heroku.com/articles/newrelic#using_new_relic_from_a_rack_app > and still get the message > "Not a Rails app, can't install New Relic plugin." after deploy to Heroku. > I added the > > configure :production do > require 'newrelic_rpm' > end > > part to config.ru > === imgpxy > Web URL: http://imgpxy.heroku.com/ > Git Repo: g...@heroku.com:imgpxy.git > Dynos: 5 > Workers: 0 > Repo size: 2M > Slug size: 724k > Stack: bamboo-mri-1.9.2 > Dyno usage: Web - 437.03 dyno-hours > Data size: (empty) > Addons: Basic Logging, Memcache 5MBs, New Relic Standard, Shared > Database 5MB > > -- > David Hall, M. Sc., da...@dpg.se > +46 (0)708-39 62 91 > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@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. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@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.
New Relic in a Rack app
I have read and followed the steps outlined for Rack apps in http://devcenter.heroku.com/articles/newrelic#using_new_relic_from_a_rack_appand still get the message "Not a Rails app, can't install New Relic plugin." after deploy to Heroku. I added the configure :production do require 'newrelic_rpm'end part to config.ru === imgpxy Web URL:http://imgpxy.heroku.com/ Git Repo: g...@heroku.com:imgpxy.git Dynos: 5 Workers:0 Repo size: 2M Slug size: 724k Stack: bamboo-mri-1.9.2 Dyno usage: Web - 437.03 dyno-hours Data size: (empty) Addons: Basic Logging, Memcache 5MBs, New Relic Standard, Shared Database 5MB -- David Hall, M. Sc., da...@dpg.se +46 (0)708-39 62 91 -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@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.
