Re: request.remote_ip
I ran into this same problem playing with Rack::Bug. I couldn't access my site and determined it was because my client IP was not in the whitelist I'd configured. I read the Rails docs and even the source and it seemed like request.remote_ip should just work... but it clearly did not. I logged all the request object's properties and saw my client IP in there, but for whatever reason request.remote_ip always returned Heroku's load balancer's IP and not my real client IP. In the end I side-stepped the problem and just setup a password for access. -- 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: blocked in china
I wonder if the GFW blocks all Amazon EC2 IPs? It would make sense, to reduce their workload playing whack-a-mole. Everyone I know in China (3 people) use proxies to jump over the firewall, and they make it sound like its a routine matter. On Mar 10, 12:41 pm, mattsly matt...@gmail.com wrote: As of early last week, I lost all of my traffic from China, and started getting tweets from users that they couldn't hit my site. Indeed, it looks like all three Heroku proxy IPs are blocked by the GFW (Great Firewall): 75.101.145.87 75.101.163.44 174.129.212.2 Not sure what we can do about this...just kind of an FYI for everyone. And a bummer. Pesky geopolitics. Here's the service I used to test btw...pretty cool:http://www.watchmouse.com/en/ping.php Matt -- 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.
can't push today, breaking on Configuring New Relic plugin step
I tried to push about 10 times over a period of about 2 hours this morning. It keeps failing on the new relic step. Is this a temporary heroku issue, or do I need to resolve some new relic issue? - Heroku receiving push - Rails app detected - Gemfile detected, running Bundler version 1.0.3 All dependencies are satisfied - Installing Exceptional plugin from git://github.com/contrast/exceptional.git... done. - Installing quick_sendgrid plugin from git://github.com/pedro/quick_sendgrid.git... done. - Configuring New Relic plugin... ! Heroku push rejected due to an unrecognized error. Please try again later. error: hooks/pre-receive exited with error code 2 -- 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.
Re: can't push today, breaking on Configuring New Relic plugin step
I talked with Heroku staff, and its a known bug with the newrelic plugin. They are working on a fix, but the immediate solution is to just remove the addon. On Nov 10, 11:46 am, marcel mpoi...@gmail.com wrote: I tried to push about 10 times over a period of about 2 hours this morning. It keeps failing on the new relic step. Is this a temporary heroku issue, or do I need to resolve some new relic issue? - Heroku receiving push - Rails app detected - Gemfile detected, running Bundler version 1.0.3 All dependencies are satisfied - Installing Exceptional plugin from git://github.com/contrast/exceptional.git... done. - Installing quick_sendgrid plugin from git://github.com/pedro/quick_sendgrid.git... done. - Configuring New Relic plugin... ! Heroku push rejected due to an unrecognized error. Please try again later. error: hooks/pre-receive exited with error code 2 -- 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.
automatic plugin installation seems counter to the bundler philosophy
I've been bitten twice now by addons whose automatic plugin installation broke my app. The ease of installation is compelling, but it seems more appropriate to just install a gem via bundler. If special Heroku magic is needed, then provide a special gem, such as heroku_newrelic or heroku_exeptional. The whole point of bundler is that your app's dependencies won't just change on you when you deploy. Yet a bunch of addons require last- minute plugin installation, with no consent or warning if the plugin has been updated. Case 1: I did some monkey patching for exceptional, so that I could filter sensitive Heroku config keys out of the crash reports (AWS private keys (!), and about a dozen others). It worked great, but then a few weeks later I noticed my private API keys were back in the crash reports. Sure enough, the exceptional plugin got updated and broke my monkey patch. Case 2: I couldn't deploy today because the newrelic plugin got updated, which broke the deploy process. I think Heroku addons should move as much code as possible into regular gems, and minimize (eliminate?) the deployment magic. -- 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.
Re: Bundler upgrade to 1.0.3 to support BUNDLE_WITHOUT?
My slug used to be about 85 MB (!), but around the time that Heroku started recognizing BUNDLE_WITHOUT, my slug size dropped to 35 MB. I also noticed that Heroku's bundler reinstalls all the gems on EVERY deploy, whereas is used to only run if my gemlock changed. Thats ~5mins instead of 15seconds. -- 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.
Re: Bundler upgrade to 1.0.3 to support BUNDLE_WITHOUT?
BUNDLE_WITHOUT is currently working for me. It magically started being recognized a few weeks ago. From my heroku config output: BUNDLE_WITHOUT= test development And when I deploy: - Heroku receiving push - Rails app detected - Gemfile detected, running Bundler version 1.0.0 Unresolved dependencies detected; Installing... Using --without test development Fetching source index for http://rubygems.org/ ... -- 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.
Re: Does Heroku support sourcing a gem from within the app using the :path option in Bundler?
I think you need to point :path one folder deeper, like: gem 'devise', :path = 'vendor/gems/devise-1.0.8' -- 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.
Re: Compiled Slug size not changing after removing large gems from Gemfile
I discovered something similar about a month ago. I dug around the directory structure using heroku console, and noticed that the deleted gems still existed in the slug's .bundle folder. -- 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.
Re: Long running rake tasks freeze or crash
I believe I have read several times that cron and rake both time out eventually, and that very long running stuff should always get processed by delayed job workers. This makes sense because you're paying directly for your worker, as opposed to getting a free lunch from Heroku for that 20 hour rake task. I ran into trouble with rake tasks that took about 20 minutes or so. I thought maybe the heroku gem was crashing, or I reached a memory limit, or maybe just a hard time limit. I first reduced the output to just a . for each model I processed instead of one line message. Some tasks that previously crashed were able to complete, but the biggest rake task (most models to process) still crashed. I replaced some of the active record model creation with straight SQL, and the rake task was able to complete. Next time I plan to go directly to delayed jobs and save all that headache. -- 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.
Re: Getting a visitors ip address in your web app
Or just request.env.ip http://rack.rubyforge.org/doc/classes/Rack/Request.src/M000288.html On Oct 2, 11:55 am, Peter van Hardenberg p...@heroku.com wrote: I use this in my code -- I run my apps at foo.heroku.com with whatever the ghetto SSL option is, so YMMV. def remote_ip if forwarded = request.env[HTTP_X_FORWARDED_FOR] forwarded.split(,).first elsif addr = request.env[REMOTE_ADDR] addr end end -pvh -- 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.
Re: upload size limit?
I'm using PaperClip to crop and create thumbnails, with everything stored in S3. I'm just curious if there's any kind of hard limit on upload size to be aware of. A Flash-based solution would be superior, but I'm sure there's some pain getting everything working correctly and its not justified at the moment. -- 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.
upload size limit?
I'm curious if there is any kind of upload size (or time) limit? I saw some old discussions about a 10MB limit, but those are so old I don't trust them. I only found one place in the Heroku docs that discourages uploading files larger than 4 MB, but its not clear what the real limit is. http://docs.heroku.com/s3 -- 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.
Re: Custom error pages, we *really* need them
+1 for iframe/javascript solution I feel like the same system could be used to improve the custom maintenance mode page as well. I tested it out on my staging app the other day, and it took 15 minutes before the ugly default page was replaced by my custom page. Thats just too long! My biggest downtime for a production migration so far downtime is less than 5 minutes, which means nobody will ever see my custom page. -- 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.
Re: Bundler 1.0.0 Rollout
No. Fortunately this isn't an absolute requirement for me (yet), so I decided to put it off in hopes that Heroku will update their bundler system to respect the :production group. On Sep 15, 10:02 am, Steve Odom steve.o...@gmail.com wrote: Marcel, Did you ever figure out a hack to haver bundler recognize your osx platform? Steve -- 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.
Re: Best way to handle sitemaps
Varnish itself can handle gigabytes of cache, because it uses the hard disk via virtual memory. But the varnish layer is shared by all heroku apps, and who knows what exactly Heroku is doing to tweak how it works. -- 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.
Re: Bundler 1.0.0 Rollout
I tried Pasha's suggestion, but it looks like the environment variable is ignored by bundler in heroku. I added autotest-fsevent to the :development group in my gemfile, and added BUNDLE_WITHOUT=test:development to the heroku app config. But when I pushed, heroku still tried to build the native extensions and failed. I don't understand why heroku doesn't just use bundle install -- deployment (or some variation) to respect the Gemfile groups... I got another idea. Hide autotest-fsevent from Heroku by using :platforms. According to the bundler docs the platform is respected automatically. Unfortunately they don't have an OSX platform, so I randomly chose one that doesn't match Heroku just to test. platforms :mswin do gem autotest-fsevent end It worked! The gem was not installed and the push succeeded. The next step would be to hack my local bundler to make it think I'm on :mswin (or :jruby), so that the gem gets picked up locally. Important note: only the block version of :platform works due to a bug: http://github.com/carlhuda/bundler/issues#issue/590 -- 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.
Re: Best way to handle sitemaps
I think the easiest and cheapest solution is to utilize Heroku's caching layer, Varnish. http://docs.heroku.com/http-caching If you set the max-timeout to 1 week then your app only gets hit once a week... assuming the sitemaps get hit often enough to keep them in the cache. -- 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.
Re: Heroku push rejected, your slug is currently being compiled. Please try again later.
While your slug is compiling you can't push a new update. If you disconnect after you push the code, but during slug compilation, the slug will still get compiled and your app updated. It should only take a few minutes. I've had it take several hours on a few occasions, as discussed in this other thread. If that happens its a Heroku bug, so please report it. http://groups.google.com/group/heroku/browse_thread/thread/d3f99f25fe7e11b1 -- 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.
Re: How to deploy app with sensitive config information?
heroku config truncates the values by default. If you want to quickly grab your S3 key or mongohq_url, use the secret --long parameter. It should really be in the documentation. heroku config --long -- 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.
Re: free vs. paid heroku app performance
My slug is pretty big, about 50 MB, mostly due to gem dependencies. I figure I could shave about 5 MB if I spent an entire day shaving off unused bits. But I doubt this would make any perceivable difference. I don't really mind the sluggish spin up time. What I do mind is having slug compilation occasionally take 4+ hours instead of the normal 3 minutes. That means I can't show my boss the current state of the app, which is pretty embarrassing and shakes his confidence in hosting the production app with Heroku. I pointed out the slow spinup because there seemed to be a strong connection between that and the slow slug compilation. I recently upped my staging to 2 dynos (1 paid), to see if the problem goes away. -- 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.
Re: Best way to handle sitemaps
Can you store the results in memcache or mongo? How much space do all the sitemap files consume? -- 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.
Re: Backup for MongoHQ Data
There is a warning on the mongodb site about using mongoexport/ mongoimport: Neither JSON nor TSV/CSV can represent all data types. Please be careful not to lose or change data (types) when using this. For full fidelity please use mongodump. http://www.mongodb.org/display/DOCS/Import+Export+Tools#ImportExportTools-mongoexport -- 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.
Re: free vs. paid heroku app performance
Thanks for the helpful tips about keeping the app responsive. Has anyone else encountered ridiculously long slug compilation (several hours), or is it just me? Its happened on at least 4 days in the past month. I checked the heroku status page each time, but only one of the times coincided with an official heroku problem. The production app was unaffected except for the official outage. I wonder if paying for a dyno would help reduce this problem too? -- 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.
Re: Use Heroku gem from within application?
I ran into a similar need yesterday. I wanted to have a Heroku cron
task create a bundle of my app, to get a daily DB backup.
Here is my task:
task :cron = :environment do
require 'heroku'
heroku_username = ENV['HEROKU_USERNAME']
heroku_password = ENV['HEROKU_PASSWORD']
if heroku_username.nil? || heroku_password.nil?
raise Missing heroku username and/or password
end
puts Capturing bundle...
heroku = Heroku::Client.new( heroku_username, heroku_password )
bundle_name = heroku.bundle_capture bagnolia-production
puts Finished initiating capture of bundle '#{bundle_name}'
end
--
1. Add the heroku gem to your .gems file or vendor it, so its
available to your app. Require the heroku gem.
2. create a new install of Herkou::Client, which needs your username
and password. I put mine into the app's config to keep it out of
source control.
3. call an instance method on the client object. It looks like you'll
want to use add_domain(). You can see all the methods here:
http://github.com/heroku/heroku/blob/master/lib/heroku/client.rb
--
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.
unwarranted Read-only file system errors
Hoptoad reported about 20 Read-only file system errors for my app last night. It looks like its just the Rails logger trying to write the standard logging info that triggered the crash. I guess its a just a transient Heroku bug? vendor/rails/activesupport/lib/active_support/buffered_logger.rb:99:in `write' vendor/rails/activesupport/lib/active_support/buffered_logger.rb:99:in `flush' vendor/rails/activesupport/lib/active_support/buffered_logger.rb:96:in `synchronize' vendor/rails/activesupport/lib/active_support/buffered_logger.rb:96:in `flush' vendor/rails/actionpack/lib/action_controller/dispatcher.rb:125:in `flush_logger' vendor/rails/activesupport/lib/active_support/callbacks.rb:178:in `send' vendor/rails/activesupport/lib/active_support/callbacks.rb:178:in `evaluate_method' vendor/rails/activesupport/lib/active_support/callbacks.rb:166:in `call' vendor/rails/activesupport/lib/active_support/callbacks.rb:90:in `run' vendor/rails/activesupport/lib/active_support/callbacks.rb:90:in `reverse_each' vendor/rails/activesupport/lib/active_support/callbacks.rb:90:in `send' vendor/rails/activesupport/lib/active_support/callbacks.rb:90:in `run' vendor/rails/activesupport/lib/active_support/callbacks.rb:276:in `run_callbacks' vendor/rails/actionpack/lib/action_controller/dispatcher.rb:95:in `dispatch' vendor/rails/actionpack/lib/action_controller/dispatcher.rb:121:in `_call' vendor/rails/actionpack/lib/action_controller/dispatcher.rb:130:in `build_middleware_stack' vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call' vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call' vendor/rails/activerecord/lib/active_record/connection_adapters/ abstract/query_cache.rb:34:in `cache' vendor/rails/activerecord/lib/active_record/query_cache.rb:9:in `cache' vendor/rails/activerecord/lib/active_record/query_cache.rb:28:in `call' vendor/rails/activerecord/lib/active_record/connection_adapters/ abstract/connection_pool.rb:361:in `call' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/static.rb:33:in `call' vendor/plugins/hassle/lib/hassle.rb:15:in `call' vendor/rails/actionpack/lib/action_controller/string_coercion.rb:25:in `call' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/head.rb:9:in `call' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/methodoverride.rb:24:in `call' vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb: 93:in `call' vendor/rails/activesupport/lib/active_support/cache/strategy/ local_cache.rb:24:in `call' vendor/rails/actionpack/lib/action_controller/failsafe.rb:26:in `call' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/lock.rb:11:in `call' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/lock.rb:11:in `synchronize' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/lock.rb:11:in `call' vendor/rails/actionpack/lib/action_controller/dispatcher.rb:106:in `call' [GEM_ROOT]/gems/thin-1.2.6/lib/rack/adapter/rails.rb:74:in `call' /home/heroku_rack/lib/static_assets.rb:9:in `call' /home/heroku_rack/lib/last_access.rb:25:in `call' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/urlmap.rb:46:in `call' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/urlmap.rb:40:in `each' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/urlmap.rb:40:in `call' /home/heroku_rack/lib/date_header.rb:14:in `call' [GEM_ROOT]/gems/rack-1.0.1/lib/rack/builder.rb:60:in `call' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/connection.rb:76:in `pre_process' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/connection.rb:74:in `catch' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/connection.rb:74:in `pre_process' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/connection.rb:57:in `process' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/connection.rb:42:in `receive_data' [GEM_ROOT]/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine' [GEM_ROOT]/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/backends/base.rb:57:in `start' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/server.rb:156:in `start' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/controllers/controller.rb:80:in `start' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/runner.rb:177:in `send' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/runner.rb:177:in `run_command' [GEM_ROOT]/gems/thin-1.2.6/lib/thin/runner.rb:143:in `run!' [GEM_ROOT]/gems/thin-1.2.6/bin/thin:6 /usr/ruby1.8.7/bin/thin:19:in `load' /usr/ruby1.8.7/bin/thin:19 -- 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.
Re: custom post_commit hook?
We don't use capistrano, but I guess I could accomplish the same thing by writing a simple rake task to first push to heroku, then call some heroku rake tasks. On Aug 5, 2:20 pm, David Balatero dbalat...@gmail.com wrote: I set my cap deploy to do a git push heroku master, then deploy to my Resque machines on EC2. Works like a charm, just requires your team to use cap deploy instead of git push. On Wed, Aug 4, 2010 at 3:18 PM, marcel mpoi...@gmail.com wrote: I'd like to run a few things after I deploy, like clear out memcache and send a deploy message to NewRelic. Is there a way to have heroku call a rake task or something after I push? Sure I can call 'heroku rake XXX' after I deploy, but I'd rather not have the possibility of anyone on the team forgetting. It would be even cooler if a failure of the rake task would trigger a rollback of the entire deploy... -- 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.comheroku%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.
custom post_commit hook?
I'd like to run a few things after I deploy, like clear out memcache and send a deploy message to NewRelic. Is there a way to have heroku call a rake task or something after I push? Sure I can call 'heroku rake XXX' after I deploy, but I'd rather not have the possibility of anyone on the team forgetting. It would be even cooler if a failure of the rake task would trigger a rollback of the entire deploy... -- 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.
Re: NOTICE: Memcached exiting beta
Sounds cool. But I've some questions: - I've never used memcached so I'm wondering how much can be cached in 5MB (currently I just want to use the Free plan). - What will happen if the 5MB will be exceeded (the oldest object in cache will be removed?) - Is there a way to retrieve stats on the memcache (presumably using the Heroku control panel?) Cheers, Marcel On Apr 20, 2:48 am, Oren Teich o...@heroku.com wrote: Hi all, We're excited to announce that we'll be taking memcached out of beta this week. We will have a few plans to meet different needs: 5MB - Free 100MB - $20/month 250MB - $40/month 1GB - $90/month 10GB - $800/month 50GB - $3500/month All existing users of the memcached add-on will be grandfathered for 2 weeks. After two weeks, you will be charged at the 100MB plan level ($20/month). Please let me know if you have any questions. Oren -- 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 athttp://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.
Re: sass_on_heroku / hassle
Thanks morgoth, Will try this later. I guess more people are interested in using haml/sass/compass within their rails app on heroku. Perhaps a FAQ can be written on heroku.com how to implement it. I googled and found this http://blog.heroku.com/archives/2009/8/18/heroku_sass/ but I guess this points people to the wrong directions, as hassle didn't work. Perhaps http://github.com/merbjedi/hassle should be merged? On Mar 28, 11:19 pm, morgoth w.wnetr...@gmail.com wrote: You can try merbjedi fork of hassle:http://github.com/merbjedi/hassle It this wont help, you can use Rack::Static middleware like this: remove hassle change your sass (compass) settings: config.css_dir = tmp/public/compiled/stylesheets Create initializer with code: ActionController::Dispatcher.middleware.use Rack::Static, :root = tmp/public, :urls = [/compiled/stylesheets] This will always compile your sass files to tmp and serve them by rack static module. -- 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.
Re: sass_on_heroku / hassle
Hi Oren,
I couldn't find this information on the hassle github page.
Do you know if Hassle is advised to used by Heroku?
The page and the information on Heroku website seem to be 'outdated'.
Heroku.com still mentions sass_on_heroku but it's github page says
it's deprecated for pedro's Hassle.
Cheers,
Marcel
On Mar 26, 6:40 pm, Oren Teich o...@heroku.com wrote:
hassle stores the stylesheets in varnish, cached for all dynos.
Oren
On Fri, Mar 26, 2010 at 6:30 AM, Marcel Overdijk
marceloverd...@gmail.comwrote:
As I understand sass_on_heroku or better hassle can be used to compile
sass stylesheets to the /tmp folder on Heroku. I'm wondering what the
findings are about using this approach.
I'm asking because of this mention in the Heroku docs. Especially the
last sentence.
There are two directories that are writeable: ./tmp and ./log (under
your application root). If you wish to drop a file temporarily for the
duration of the request, you can write to a filename like
#{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that
this file will be there on subsequent requests (although it might be),
so this should not be used for any kind of permanent storage.
Cheers,
Marcel
--
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.comheroku%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.
Re: sass_on_heroku / hassle
I tried to use hassle today but without succes.
Locally it works but on Heroku server the stylesheet cannot be found.
I've used both
= stylesheet_link_tag application.css
link href=/stylesheets/application.css media=screen
rel=stylesheet type=text/css /
in my layout, but it just can't find /stylesheets/application.css
Note that when I'm running my app locally it writes the compiled css
to ./public/stylesheets and not in ./tmp. Don't know if this should be
the case either?
On Mar 26, 6:40 pm, Oren Teich o...@heroku.com wrote:
hassle stores the stylesheets in varnish, cached for all dynos.
Oren
On Fri, Mar 26, 2010 at 6:30 AM, Marcel Overdijk
marceloverd...@gmail.comwrote:
As I understand sass_on_heroku or better hassle can be used to compile
sass stylesheets to the /tmp folder on Heroku. I'm wondering what the
findings are about using this approach.
I'm asking because of this mention in the Heroku docs. Especially the
last sentence.
There are two directories that are writeable: ./tmp and ./log (under
your application root). If you wish to drop a file temporarily for the
duration of the request, you can write to a filename like
#{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that
this file will be there on subsequent requests (although it might be),
so this should not be used for any kind of permanent storage.
Cheers,
Marcel
--
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.comheroku%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.
Re: sass_on_heroku / hassle
Got it working now, but not as I want...
As long as ik keep sass templates in ./public/stylesheets/sass
and include stylesheets from /stylesheets in html page everything
works fine.
However I like to change the template location of the sass templates
to ./app/stylesheets using Sass::Plugin.options[:template_location] =
./app/stylesheets.
But when I do this it won't work anymore.
Next to that I would also change Sass::Plugin.options[:css_location] =
./public/stylesheets/compiled
So I can easily add this folder to .gitignore.
I'm wondering if this possible with the hassle plugin. Any help
appreciated.
Cheers,
Marcel
On Mar 26, 6:40 pm, Oren Teich o...@heroku.com wrote:
hassle stores the stylesheets in varnish, cached for all dynos.
Oren
On Fri, Mar 26, 2010 at 6:30 AM, Marcel Overdijk
marceloverd...@gmail.comwrote:
As I understand sass_on_heroku or better hassle can be used to compile
sass stylesheets to the /tmp folder on Heroku. I'm wondering what the
findings are about using this approach.
I'm asking because of this mention in the Heroku docs. Especially the
last sentence.
There are two directories that are writeable: ./tmp and ./log (under
your application root). If you wish to drop a file temporarily for the
duration of the request, you can write to a filename like
#{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that
this file will be there on subsequent requests (although it might be),
so this should not be used for any kind of permanent storage.
Cheers,
Marcel
--
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.comheroku%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.
Re: sass_on_heroku / hassle
I guess I confused myself ;-)
For now I also decided to just use compass/sass without hassle and
commit the compiled css files to git.
On Mar 27, 5:34 pm, Oren Teich o...@heroku.com wrote:
Hi Marcel,
What's the confusion? As the github page says, sass_on_heroku is now
hassle. You should use that one. Which info on the heroku site is
outdated?
Oren
On Sat, Mar 27, 2010 at 5:50 AM, Marcel Overdijk
marceloverd...@gmail.comwrote:
Hi Oren,
I couldn't find this information on the hassle github page.
Do you know if Hassle is advised to used by Heroku?
The page and the information on Heroku website seem to be 'outdated'.
Heroku.com still mentions sass_on_heroku but it's github page says
it's deprecated for pedro's Hassle.
Cheers,
Marcel
On Mar 26, 6:40 pm, Oren Teich o...@heroku.com wrote:
hassle stores the stylesheets in varnish, cached for all dynos.
Oren
On Fri, Mar 26, 2010 at 6:30 AM, Marcel Overdijk
marceloverd...@gmail.comwrote:
As I understand sass_on_heroku or better hassle can be used to compile
sass stylesheets to the /tmp folder on Heroku. I'm wondering what the
findings are about using this approach.
I'm asking because of this mention in the Heroku docs. Especially the
last sentence.
There are two directories that are writeable: ./tmp and ./log (under
your application root). If you wish to drop a file temporarily for the
duration of the request, you can write to a filename like
#{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that
this file will be there on subsequent requests (although it might be),
so this should not be used for any kind of permanent storage.
Cheers,
Marcel
--
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.comheroku%2bunsubscr...@googlegroups.com
heroku%2bunsubscr...@googlegroups.comheroku%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.comheroku%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.
sass_on_heroku / hassle
As I understand sass_on_heroku or better hassle can be used to compile
sass stylesheets to the /tmp folder on Heroku. I'm wondering what the
findings are about using this approach.
I'm asking because of this mention in the Heroku docs. Especially the
last sentence.
There are two directories that are writeable: ./tmp and ./log (under
your application root). If you wish to drop a file temporarily for the
duration of the request, you can write to a filename like
#{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that
this file will be there on subsequent requests (although it might be),
so this should not be used for any kind of permanent storage.
Cheers,
Marcel
--
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.
Re: European data center?
+1 On Mar 23, 6:40 pm, Joost Saanen stalk...@gmail.com wrote: I am Curious too. regards Joost On 22 March 2010 19:30, Josh Huckabee joshhucka...@gmail.com wrote: Bump. Any official word on this? This would definitely be nice to have. On Mar 19, 8:14 pm, Arto Bendiken arto.bendi...@gmail.com wrote: This has been asked a couple of times [1, 2] before, but do you have a time frame for expanding the Heroku offering to Amazon's European data center (eu-west-1 in Ireland)? Needless to say, those of us building Rails applications primarily targeting the 500 million people living here in the EU are awaiting this development with bated breath ;-) I'm currently involved in building yet another Amazon ELB-based cluster from the ground up, and I can't help thinking how much I'd prefer to build it on the Heroku platform instead. Best regards from sunny Spain, Arto -- Arto Bendiken |http://www.makalumedia.com/ [1] http://groups.google.com/group/heroku/browse_thread/thread/826d629731... [2] http://groups.google.com/group/heroku/browse_thread/thread/5b113a910c... -- 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.comheroku%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.
newrelic - apdex score T
Is it possible to change the apdex score for my heroku app? I found only this, http://support.newrelic.com/faqs/general/how-do-i-set-apdex-t . -- 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.
