Re: New Postgress Plans
All plans on Heroku are shared in one way or another. Even our biggest instances run on top of AWS, using their VMs. We've moved away from calling any of the databases dedicated, and instead focused on what you get. Identify how much cache you're looking for, and just choose the DB that fits. Oren On Mon, Aug 6, 2012 at 2:12 PM, Jeff Schmitz jeffrey.j.schm...@gmail.comwrote: Does anybody know (I can't figure from the web site) at which level the plan has a dedicated database. I think it used to call Ronin and above dedicated plans, but I don't see that any more. For the new Crane and Kappa plans, I haven't ever seen it mentioned, so I assume they are shared or VMs Anybody know? jeff -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: Heroku + remote database
There is no single IP address you can restrict it to. Every request from Heroku may come from a different IP address. If you're running on EC2, you can use their security groups feature to open it to Heroku servers. https://devcenter.heroku.com/articles/external-services On Sun, Jul 29, 2012 at 11:25 PM, Alex Tomás lance...@gmail.com wrote: Hello, I'm trying to connect from Keroku to my database server. How I can do? I know I have to give permission to my server, but at what IP? Thanks -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: Heroku Access Through Firewall
Due to our dynamic nature, there is no way to limit it to a small or single IP address. We automatically change IP addresses at various times due to load, performance, infrastructure changes, etc. This is a common design feature for cloud these days. Right now your CNAME setup will round-robin between 8 or so IP addresses, and we find historically that at least one will change every week or so. If you use the SSL add-on, you'll have a single IP address… for a while. It's non-deterministic when it will change, with no control available. It could change every few minutes, or only once a month. Oren On Mon, Aug 6, 2012 at 5:08 PM, Karl threadh...@gmail.com wrote: I have an app that is B2B, utilizing a custom domain. Occasionally, I get an email from a new corporate firewall admin asking for the url, ports and ip's of the application. The url (mydomain.com) and ports(80, 443) are easy, but I'm having problems with the IP address. They (company firewall admins) complain that the application does not have a single IP address. Every time they hit the app, it comes back with a different IP. I know every firewall is different, and maybe a proxy and filter are the best methods to handle this. But I need to give them some guidance. Can someone give me some tips on what to tell firewall administrators what to do to allow access to a Heroku application? -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Backed up approvals
FYI, google groups is having issues, and we are unable to approve any pending messages. Existing members who have successfully emailed the list before should continue to work. New members who haven't posted are automatically held for spam moderation. Oren -- 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: Automatic restart of dynos every day?
We restart dynos at least once every day, and sometimes more often. http://devcenter.heroku.com/articles/dyno-manifold#dyno_restarts You should see something in the logs however. If you don't see anything please drop support a ticket. Oren On Mon, Feb 6, 2012 at 9:07 AM, Guillaume Coderre guilla...@rougeoxyde.comwrote: Hi, I've posted this message yesterday, but it's not appearing in the group, so I'll go ahead and post again. I know that Heroku periodically restarts dynos to relocate them, but our dynos (according to New Relic) are being restarted every day at about 3:45 PM. Is this normal? More surprising is the fact that we can't see any log entry when the restart happens. Thanks for your help! -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/Y6w_JrWoS7UJ. 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.
Re: Newb question on static assets
This should be automatic. You can use some plugins like firebug to check headers. On Fri, Jan 27, 2012 at 8:32 AM, Carson Gross carsongr...@gmail.com wrote: Hi Oren, Thanks for the links. After reading through them, my best theory for the reason Chrome is aggressively reloading some resources I'd prefer that it didn't is because of the relatively recent Last-Modified headers coming from Varnish. Is there a way to tie the Last-Modified header back to when we last deployed? Thanks, Carson On Jan 26, 10:22 pm, Oren Teich o...@heroku.com wrote: There are different types of caches - client and server side. Check out this presentation to learn more about what's going on: http://tomayko.com/writings/railsconf-caching-talkhttp://www.slideshare.net/rtomayko/https-bestkept-secret-cachinghttp://tomayko.com/writings/things-caches-dohttp://tomayko.com/writings/rack-cache-announce Oren On Thu, Jan 26, 2012 at 9:53 PM, Carson Gross carsongr...@gmail.com wrote: And one last note: due to the way some of these resources are included (e.g. the stylesheet_link_tag method in rails) they end up with a query string. Reading online, it appears that resources with a query string are not supposed to be cached, but that the major browsers ignore that. Anyone know for sure? Thanks, Carson On Jan 26, 9:41 pm, Carson Gross carsongr...@gmail.com wrote: OK, now that I have my head around what is going on, it appears that the static stuff is being cached and served up via Varnish. It appears that my browser is not respecting the varish response though. The response has the following header: Cache-Control:public, max-age=43200 and yet another request is made when I hit cmd-r. When I click around, I still see requests for this resource, with the 304 response code. I'm using Chrome. UPDATE: OK, digging a bit more, I found this page: http://code.google.com/speed/page-speed/docs/caching.html In particular, I note this bit: Set the Last-Modified date to the last time the resource was changed. If the Last-Modified date is sufficiently far enough in the past, chances are the browser won't refetch it. And, looking more closely at the response headers, I see this: Cache-Control:public, max-age=43200 Connection:keep-alive Date:Fri, 27 Jan 2012 05:31:46 GMT Last-Modified:Thu, 26 Jan 2012 17:14:44 GMT Server:nginx Via:1.1 varnish X-Varnish:800861986 And note that the Last-Modified date is today, even though we haven't deployed a new version of our app for a while, which I believe may be why Chrome is issuing requests for the resources even though it isn't changing. When I resubmit, I see a different Last-Modified header for the same resource. So my guess here is that the Last-Modified header is generated by the change date of the file on a particular instance of Varnish, and that various instances are coming up and going down, causing the Last Modified date to be relatively recent, causing Chrome to submit more requests to the server than I'd like. Does that sound at all plausible? Thanks, Carson On Jan 26, 5:56 pm, Carson Gross carsongr...@gmail.com wrote: Looking at it a bit more (as well as some *yikes* requests to our server) I see that we are getting a ton of 304s, which are, no doubt, tying up our dynos. So, this may be more of a rails question than a heroku question, but how can I set expires headers on certain static directories? Yes, I am a complete and utter newb at this. Cheers, Carson On Jan 26, 5:00 pm, Carson Gross carsongr...@gmail.com wrote: Heya, Sorry, digging through the docs I couldn't really get an answer on this that I understand: So, with static assets, deployed on the bamboo-ree-1.8.7 stack, are static assets served by web dynos? As our application has grown over time, we've evolved to issue a horrific number of requests for static content (css, javascript, etc.) and I'm trying to understand just how bad that is for our performance. Seems like we'd be tying up web dynos, but I want to make sure. Secondly, given that I don't feel like rewriting all that code right now, is there a way to map certain paths to a heroku app to another server, so we aren't hammering our dynos so badly? Thanks, Carson -- 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 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 heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more
Re: Added custom domain gives error that domain is owned by another user. Why?
This means that some other app on heroku has your domain already. If you're using cloud app with cusomdomains, or some other piece of software you will run into this. Best bet is to submit a support ticket. Oren On Mon, Sep 19, 2011 at 3:18 PM, Turadg Aleahmad tur...@gmail.com wrote: Josh, was this resolved? I'm facing the same issue and it's very frustrating. -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/nNd644mmz80J. 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.
Re: Is it possible to `git push` heroku config:add or just not restart the app?
It's not documented because it's not an officially supported feature. It is strongly encouraged to not depend on env variables that you do not personally define. a git hook may get you what you want: http://www.kernel.org/pub/software/scm/git/docs/githooks.html Oren On Sun, Aug 7, 2011 at 8:04 AM, Keenan Brock kee...@thebrocks.net wrote: Hi You can get some ideas by going into heroku console and typing `env` --Keenan On Sunday, August 7, 2011 at 1:34 AM, kowsik wrote: It's the same as 'git rev-parse --short HEAD'. AFAIK, it's not documented anywhere, found it just out of curiosity on what ENV's heroku sets for the app. Someone from Heroku has to confirm this. Like I said, just happened to noticed this, but it seems to correlate with running 'git rev-parse --short HEAD' against my repo after each push. YMMV, K. --- http://blitz.io @pcapr On Sat, Aug 6, 2011 at 6:54 PM, dblock dblockdot...@gmail.com wrote: For some reason I thought that was different ... Is this documented somewhere on Heroku? Forgive my ignorance, is it just the first 7 digits of the commit hash? Why 7? Also, I found this thread http://groups.google.com/group/heroku/browse_thread/thread/35886af3ee8a87f6 that wasn't answered and looks worrisome - is this guaranteed to be what has been pushed? Thx dB. On Aug 5, 4:46 pm, kowsik kow...@gmail.com wrote: If you do $ heroku console 'ENV' on your app, you'll notice that all heroku apps already have a COMMIT_HASH environment variable that's the last git push/commit revision. You can simply use this instead of defining your own config variable. K. ---http://blitz.io @pcapr On Fri, Aug 5, 2011 at 1:37 PM, dblock dblockdot...@gmail.com wrote: We use a CDN for our content. Every new push to heroku changes the value of ASSETS_HASH to the git-revision of the latest change. Then the system reads that value to make URLs. I don't want to commit a file that contains ASSETS_HASH because that becomes a chicken-egg problem (a hash that represents the ... previous commit, umh...), I am super happy with our heroku config:add ASSETS_HASH=... . But that restarts the server, after which I am pushing the new code, maybe 30 seconds later. Is it possible to combine those two? I see two options. - git push heroku master +++config:add ASSETS_HASH=... - heroku config:add ASSETS_HASH=... --norestart ; git push heroku master Ideas? Thx dB. -- 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 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 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. -- 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.
Re: Official source to identify Heroku's SSH host key?
Hi Todd, Great question. Posted a new devcenter article with the details here: http://devcenter.heroku.com/articles/git-repository-ssh-fingerprints Oren On Wed, Jun 15, 2011 at 9:59 AM, Todd A. Jacobs nos...@codegnome.org wrote: When attempting to push to Heroku from a new machine: $ git push heroku master The authenticity of host 'heroku.com (50.19.85.132)' can't be established. RSA key fingerprint is 8b:48:5e:67:0e:c9:16:47:32:f2:87:0c: 1f:c8:60:ad. This is expected, but I have no mechanism for verifying authenticity of the host key. A search of the Heroku dev center docs turns up nothing relating to the host key, nor is there an SSHFP or TXT record in DNS. It seems like something that should be easier to find in the developer docs. In the meantime, can anyone point me to an official source validating the fingerprint? -- 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.
Re: Using MongoHQ or Cloudant for Audit Trails
We launched replication into beta this week. We have many large customers using it already in production. Drop a note to b...@heroku.com and he can hook you up with the details. Oen On Fri, Jun 17, 2011 at 9:16 PM, Karl threadh...@gmail.com wrote: 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. -- 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 petters...@gmail.com 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.
Re: 503 error when decreasing dynos
I believe what's missing here is that thin is the process receiving the sigterm, and doesn't respond correctly. Instead of using sigterm as a notice to quit when it can, it treats sigterm as a -9 equivalent. This is a bug in older versions of thin. We've worked with the thin maintainers to get this fixed, and the newest versions do now handle sigterm correctly. If you are on bamboo, you can put thin in your gemfile on the latest version (1.2.11) and you'll get the correct behavior responding to signals. However there are dependencies between older versions of ruby and older versions of thin, so if you aren't running the latest rails, you may not be able to use the latest thin. This is why we haven't deployed it by default to all apps. Yes, we need to document this better. Sorry about the confusion. Oren On Thu, May 12, 2011 at 1:11 PM, midwaltz ste...@gmail.com wrote: Interesting, thanks Peter. Yes, that's probably worth documenting. Two questions: - Are requests in the queue somehow pre-assigned to a specific dyno? I'm asking because I'm testing this behavior on a bare sinatra app with a get handler that sleeps for 0.5 seconds and then returns 'OK'. In other words the request takes half a second, so according to you it should be quick enough to finish before being sent a SIGKILL. But I keep seeing those errors, so I'm guessing either Sinatra panics and kills itself on SIGTERM, or maybe it's a queue thing? I'll be happy to share the code I'm using to make the tests if you'd like. (I'm using the default Sinatra gem (not specifying a version) on the bamboo- ree-1.8.7 stack). - How do I catch a SIGTERM during a Sinatra app request? On May 12, 10:15 am, Peter van Hardenberg p...@heroku.com wrote: We normally send a SIGTERM, then wait five (ish?) seconds to let the last request serve and then, then send SIGKILL if the process still hasn't gone away. You can confirm this behaviour here by catching and logging the SIGTERM in your app and then reproducing the situation you describe. If you can provide a test-case that shows you're not seeing expected behaviour (I use it extensively in one of my test apps) I'll make a ticket gets filed against the Runtime. Otherwise, maybe there's somewhere we can improve our documentation here. Regards, Peter Heroku On Wed, May 11, 2011 at 8:49 PM, midwaltz ste...@gmail.com wrote: When decreasing Dynos while they are busy, some of them return a 503 status error with Heroku error code H13 (Connection closed without response http://devcenter.heroku.com/articles/error-codes#h13__connection_clos. .. ). I can only speculate, but to me it looks like instead of waiting for the Dyno to finish sending its request, the Dyno is killed right away. After a quick Googling I found out this bug might have been known for a while: http://www.continuousthinking.com/2010/11/3/heroku-autoscaling-bug (except the error status codes look different, but it might have been a misstep?). What's the status on fixing this bug? Cheers, Steph -- 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. -- 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: Git commands within app
Hello, your app is not a git repo when running on Heroku. If you want to show some git based info, your best bet is to use a hook locally to write out the information to a file then send that up to Heroku. Oren On Sat, May 7, 2011 at 3:53 AM, Clément clmntlx...@gmail.com wrote: Hi, Does an app have a reference to its git repo ? I mean : I have any chance to retrieve the last commit within the app itself ? I would like somthing like : %= `git show HEAD` % which works well on my computer but not once deployed on Heroku :/ Thanks, Clément -- 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.
Re: strftime doesnt parse %N
I believe this is a ruby 1.9.2 feature. Simply use the 1.9.2 bamboo stack. Oren On Wed, Apr 20, 2011 at 2:39 PM, sebastian greatful sebastianthegreat...@gmail.com wrote: On every other host then heroku I can pass %Y:%m:%d %H:%M:%S.%6N to strftime and it returns the expected result: 2011:04:14 22:52:52.758612000 however on Heroku I get 2011:04:14 22:52:52. %6N. So obviously heroku's strftime lib doesnt parse %N and I need second decimals. Can anyone suggest an alternative way to return the complate timestamp or is a heroku support ticket requesting an upgrade in place? -- 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.
Re: Limits for Memcache add-on
There are no hard limits on the bandwidth usage with memcache. Oren On Wed, Apr 20, 2011 at 2:43 PM, Jaime A othello...@gmail.com wrote: While studying the different option for my project, I am starting to look at MemCache add-on - http://addons.heroku.com/ Are there any hard limits on the amount of transactions or bandwidth I will be permitted to use? Say I signed for a 1GB of Memcache, would I be permitted to do the same amount of transactions p/minute as if I was to purchase a 10GB of MemCache? Alternatively, is there a bandwidth limit instead (only allow X amount of say 50KB objects per minute) or are you allow to hit the MemCahe with as many transactions as you possibly can without been worry about any limits. It will followed that since resources are shared, a particular limit has be set otherwise a process could overwhelm/slow the cache servers, but I am not able to find those limits on your site :( Thx. -- 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.
Re: Dyno wake up processing
Nothing exists between requests on the filesystem. If you need to persist something, you need to put it in a persistent store - memcache, S3, the database, etc. Oren On Tue, Mar 8, 2011 at 8:12 AM, Wes Gamble we...@att.net wrote: The files comprise a cache that needs to be there for the next user, even if that user is the one who's unfortunate enough to wake up the app. W On 3/8/11 9:54 AM, Miles Smith wrote: I always assume my cronies is running brand new instances. Why not just check if you files are there, if not , create them. On Mar 8, 2011 3:39 AM, Wes Gamble we...@att.net wrote: Given a Heroku app.: If I have a cron job that populates a cache directory in RAILS_ROOT/tmp once a day, and all of my dynos go idle, when they wake up, will the tmp directory be empty or will it still contain what my cron job wrote? (I think the deeper question here is whether a dyno wakes up in some pre-existing state, or whether a dyno. is simply reconstituted from the slug state at deploy-time? I apologize if my phrasing is awkward/imprecise.) If tmp will be empty, do we have any way to hook into the dyno wake-up process in order to do some filesystem initialization in /tmp? Thanks, Wes -- 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. -- 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.
Re: Most popular (view counts), performance and Varnish cache
There are many ways of doing this. Track page views with Google Analytics, and query every now and then to get your top app list. Will work with varnish. Track page views in your app via a javascript post onload. Will work with varnish. Track page views in your app. Won't work with varnish. Think about action caching with memcache instead possibly. ORen On Tue, Mar 1, 2011 at 6:05 PM, Russell Quinn m...@russellquinn.com wrote: Hey everyone, I'm building a website that needs to list articles ranked by how popular the are (i.e. page views.) Does anyone have any ideas of how to implement this in an optimised way using Rails 3 on Heroku? The article pages are going to be heavily cached by the Varnish layer too, so I'm at odds to how do this. Thanks, Russell. -- 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.
Re: Duplicate logging request with SSL
This is normal. You can see the source of one is 127.0.0.1, that is us making a http request after terminating your https request. On Mon, Feb 28, 2011 at 1:39 AM, Andy Shipman a...@cllearview.com wrote: Hello there, Checking out the logs for my app, which runs over SSL, I have two lines for each and every request to the app, i.e: 2011-02-28T01:33:22-08:00 heroku[nginx]: GET / HTTP/1.0 | 127.0.0.1 | 8747 | http | 200 2011-02-28T01:33:22-08:00 heroku[nginx]: GET / HTTP/1.0 | 10.198.119.180 | 8747 | https | 200 Is this normal for SSL with nginx? Are there any performance issues with this duplicate request? Have I configured the app incorrectly somehow? Thanks, Andy Shipman -- 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.
Re: SSL only site Caching problem
You can't use varnish caching and redirects. You can cache you stuff in memcache instead and then perform filtering in the app. Oren On Fri, Feb 25, 2011 at 7:01 AM, Cristiano cbe...@gmail.com wrote: I have a bit of a problem. I want my site to only work on SSL, so I have setup a before_filter to redirect to HTTPS if needed. The problem is that if I cache a page (and even if it get's cached on https) the page can then get loaded on http without being redirected. I imagine the way to solve this is to split apart the cache for https and http, or to somehow handle the redirect in nginx rather than in my app. Is there any way to do this or am I screwed? -- 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.
Re: Varnish http-cache post requests
Varnish does not cache post requests. On Tue, Feb 22, 2011 at 5:08 PM, ryan ryanst...@gmail.com wrote: I have a facebook application in process and would really like to use the varnish http caching, however facebook makes all requests in an iframe post by default. Will varnish cache POST requests? (It seems that by definition POST requests should not be cached, but I wanted to check if varnish might ignore this). Thanks, Ryan -- 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.
Re: PGError: FATAL: sorry, too many clients already
hi Jim, Actually we were on this around 10:15 last night. The mistake was that the on-call engineer decided not to update the status site immediately. Once he started working he got caught up, and our automated systems to remind us to update status weren't active since we hadn't posted an update in the first place. We are changing our process to ensure that all outages are immediately posted. We will also post a post-mortem on the issue in the next day or two. Oren On Wed, Feb 2, 2011 at 6:30 AM, Jim Gilliam j...@gilliam.com wrote: This happened to my app as well last night. http://act.ly/ was down for roughly 7 hours. A drive on the shared database failed, the database was corrupted and they had to restore from a backup. My app was down from 9:49pm PT to 4:45am PT. I submitted an urgent support ticket at 11:14am PT. There was no acknowledgement on status.heroku.com until 2:21am PT I am a huge heroku fan, but this *really* concerns me. It means that no automated system caught this failure AND no one saw my urgent app is down support ticket for as much as 4 hours. Jim Gilliam On Wed, Feb 2, 2011 at 5:15 AM, John Beynon j...@beynon.org.uk wrote: there has been trouble with some shared databases this morning - http://status.heroku.com/ -- 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. -- 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: Bundler was not upgraded fully
try touching your Gemfile, rerunning bundle install locally to ensure you have a new Gemfile.lock, and pushing again. On Wed, Feb 2, 2011 at 7:40 PM, Vitaliy Khustochka xyc...@gmail.com wrote: Hi! In my app's Gemfile I have some option incompatible with old versions of Bundler, actually this is :platforms = :mingw option. So I was very glad when it was announced that bundler will be upgraded to version 1.0.7. So, after the date when it was supposed to be upgraded I ran git push heroku and it seems to be OK: all dependencies resolved, using bundler 1.0.7: - Heroku receiving push - Rails app detected - Detected Rails is not set to serve static_assets Installing rails3_serve_static_assets... done - Gemfile detected, running Bundler version 1.0.7 And it say application was launched. But when I navigate to my app in the browser I see 'App Crashed' message, and when I make heroku logs I see the following: == dyno-1571599.log (crash) == /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/dsl.rb: 211:in `_normalize_options': `mingw` is not a valid platform. The available options are: [:mri_18, :mri_19, :jruby, :ruby_18, :mswin, :ruby, :ruby_19, :mri] (Bundler::DslError) Please pay attention - it says bundler 1.0.3 is used. So it looks like bundler was upgraded where the dependencies is resolved but it was not on the dyno where the app is actually executed. -- 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.
Re: Help getting app to start running?
You seem to be missing whatever provides Digest. Does it run locally if you create a blank gem set in RVM (rvm create 1.9.2@blank - make sure you don't have default gems by running gem list in that gemset). Oren On Sun, Jan 30, 2011 at 9:56 AM, Jason Preston jasonp...@gmail.com wrote: Unfortunately it gives me the same error. I even went ahead and commented the group :development blockin my Gemfile just in case there was something I'm requiring for dev that is being left out of production and breaking it...no dice. Just for fun I tried migrating to 1.8.7 to see if it ran -- it does not. The logs produce the same output every time. Anything else I can provide that would help determine what it's even looking for? It boggles my mind that it runs locally - I don't even have ruby 1.9.1 installed... On Jan 30, 8:43 am, Scott LaBounty slabou...@gmail.com wrote: When I tried something similar, I didn't have much luck with migrating a stack. Try creating a new project with 1.9.2 initially and then your push. That may work better. Scott On Sun, Jan 30, 2011 at 12:40 AM, Jason Preston jasonp...@gmail.com wrote: I've put the output from $ heroku logs on pastie for reference: http://pastie.org/1511022 I have an app that runs beautifully on ruby 1.9.2 and rails 3.0.3 in my local rvm environment, but after pushing to heroku and doing heroku stack:migrate to bamboo-mri-1.9.2 my app will not start. I don't really fully understand the output I'm getting from the logs, especially given that it appears to be trying to load something from ruby 1.9.1. Has anyone seen this before? Any idea why the app is crashing on heroku but running on local? I can't even tell what file it's trying to load and not finding...and WHY is it trying to load 1.9.1 if I'm running 1.9.2?? Any help would be much 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.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. -- Scotthttp://steamcode.blogspot.com/ -- 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.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 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: getting the root of my domain pointed to proxy.heroku.com
You can't - you need to setup A records. http://docs.heroku.com/custom-domains#dns-setup On Sun, Jan 30, 2011 at 10:10 AM, JDeville jeffdevi...@gmail.com wrote: This is really a dns question, but my provider isn't being very responsive. What dns record to I need to add, to make the root of my domain (wishgenies.com) point to proxy.heroku.com? I can create a cname for www.wishgenies.com, but I can't do that for the domain root. Thanks! -- 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.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 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: Understanding DATABASE_URL vs. SHARED_DATABASE_URL
the SHARED_DATABASE_URL is set because all apps on Heroku come with a share database. It is not used by itself. The DATABASE_URL is the URL used by all tools. You can ignore the SHARED_DATABASE_URL in this case. ORen On Tue, Jan 25, 2011 at 3:54 PM, Wes Gamble we...@att.net wrote: I have a Heroku Rails app. that I wanted to point to another DB (used by a different Heroku app.), so I forced it's DATABASE_URL to a specific value (I am aware that Heroku _officially_ doesn't guarantee that that DATABASE_URL changes out from under the app.). This app. has a SHARED_DATABASE_URL value that is different from the value for DATABASE_URL. I notice that when I use the pgbackups add-on to do a backup, the DATABASE_URL is getting backed up, which is what I want. 1) Does the SHARED_DATABASE_URL actually matter if my DATABASE_URL value is different? 2) Should I force the SHARED_DATABASE_URL value to be the same as my DATABASE_URL value? 3) Why does pgbackups back up the DATABASE_URL instead of the SHARED_DATABASE_URL? Thanks, Wes -- 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.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 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: Security vulnerability
You do not need to take any action. Heroku will restart you app when we change the credentials automatically. Oren On Fri, Jan 21, 2011 at 9:42 AM, Neil Middleton neil.middle...@gmail.comwrote: Just reading the email regarding the fixed security vulnerability (If you've not got it yet, you will). In there it states that all the add-on credentials will be updated at some time over the next week, and that we must restart apps in order to pick up the change. Does this mean that stuff will stop working until we restart once the credentials are changed? -- Neil Middleton http://about.me/neilmiddleton -- 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.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 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: Block On File Upload
A dyno is the entire stack. A request, the second it hits Heroku, blocks a dyno. This could be because your application is processing, or because you are handling an upload. If you are doing decent size upload, you should have your app upload directly to S3. Oren On Sun, Jan 16, 2011 at 12:33 PM, John Maxwell jgwmaxw...@gmail.com wrote: Yeah - that is talking about the outgoing hop to S3 from Heroku - which is a blocking I/O, not the incoming step into Nginx... Any word on this from an official source? -- 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.
Re: 1 hour inactivity idling and http caching
Your app may not be setting the cache headers correctly. If your resource is cached, it will never hit the dyno. If you look at the logs, a cached hit will show up in nginx, but nothing else (e.g. no web.1 process). If you see a web.1 request, then it isn't getting cached by varnish. The only time we flush the cache is when you deploy. Idling an app will not impact cached content. Oren On Fri, Jan 7, 2011 at 3:03 AM, Martin Petrov m.p.pet...@gmail.com wrote: If this is the case then I should remove http caching in order to prevent the app from shutting down as much as possible. But... why requesting a cached page starts the app if the request is never handled by the app? On Jan 7, 11:18 am, Steve Smith st...@scsworld.co.uk wrote: I'm not an expert on this so I would double check, however I think this is all the case, If you only have one dyno then the app will shutdown when there are no requests for a certain time period. I believe this isn't the case once you have more than one dyno but in my experience at that point you have enough concurrent connections to keep things alive anyway. If you are caching the page it will be stored in varnish so the request will never be handed out to the app and will therefore allow the app to shutdown. Steve On 7 Jan 2011, at 09:02, Martin Petrov wrote: Hi, Looking at my logs I see that if my application is not used for 1 hour its state is changed from up to down. Next time a request comes it takes several seconds to start again. Does requesting an http cached page keeps the application alive? My app has only one page, which is http cached. -- 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. -- 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 debug code written for delayed_job?
you need to use our new beta logging service ASAP. http://addons.heroku.com/logging http://addons.heroku.com/loggingOren On Mon, Jan 3, 2011 at 4:02 PM, Todd profes...@gmail.com wrote: I'm curious how people go about debugging code written for delayed_job. I originally had some code that in my model that interacted with a webservice, the code was in a single method update_google_mailing_list -- I then decided to move that code into a delayed job. Whenever I call that method, I call self.delay.update_google_mailing_list -- and it has worked fine. I'm now discovering that there are some edge cases that I need to handle, and it's not clear exactly what is going wrong with the code. I'd love to hook up my debugger to see what is going on, but it's production code and I need to identify more information about the state of things. I'd love to look at the delayed_job log file, but currently this is what I see, even when I do logger.info() == dyno-1491696.log == Exceptional::Config.load - no configuration file Thin web server (v1.2.6 codename Crazy Delicious) Maximum connections set to 1024 Listening on 0.0.0.0:38556, CTRL+C to stop Thanks for your advice, Todd -- 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: Killing Cron Process?
heroku restart should restart all of your process, including cron. you can also remove and add the add-on Oren On Wed, Dec 29, 2010 at 10:50 AM, Zach Bailey znbai...@gmail.com wrote: I have a long-running cron process as a result of an out of control task that I need to kill. Is it possible to do this via the heroku gem or console somehow? -Zach -- 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: Wildcard subdomains with GoDaddy
Add three more records for . or yourdomain.com. you need 6 if you're using wildcard - three for the wildcard, three for the root domain. Oren On Mon, Dec 20, 2010 at 11:15 AM, Barry Welch btwel...@gmail.com wrote: I am also having trouble with GoDaddy + Heroku with wildcard subdomains In my setup, since GoDaddy apparently doesn't allow wildcard CNAMES, I currently have 3 A-records that look like this: A-Record * 75.101.163.44 A-Record * 75.101.163.44 A-Record * 75.101.163.44 .. with no CNAMES. Of course, this means 'http://www.mydomain.com' will load just fine, but 'http://mydomain.com' will not. Aside from changing registrars or using the Zerigo add-on, I am at a loss as to how to set this up. The Heroku documentation about wildcard domains is vague, stating: To use with a custom domain, configure your registrar to point *.yourdomain.com at heroku.com. If things are set up correctly you should be able to look up any arbitrary subdomain: ... which seems like a cop-out statement. Any ideas on this? On Nov 15, 11:57 am, Keenan Brock kee...@thebrocks.net wrote: Hi Jeff, I had it working before I switched everything over tohttp://namecheap.com/ 2 things to try: 1) try an @ instead of a * 2) try using A records instead of a CNAME (3 of them) dns numbers are athttp://docs.heroku.com/custom-domains 75.101.163.44 75.101.145.87 174.129.212.2 --Keenan On Nov 14, 2010, at 12:48 AM, Jeff wrote: Having trouble setting up GoDaddy for wildcard subdomains. I have one domain registered with Dreamhost, and it works fine. Not sure what's different with GD. I have the three A records: A @ 174.129.212.2 A @ 75.101.145.87 A @ 75.101.163.44 But I can't set up a CNAME like this: * CNAME proxy.heroku.com. With DH, this works. But with GD, I can't find the right way to handle. Any ideas? -- 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.- Hide quoted text - - Show quoted text - -- 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. -- 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 and custom domain with Dreamhost
Wait 24 hours, and check again. DNS by its nature takes a while to get all around the internet. On Sun, Dec 19, 2010 at 7:29 PM, Braxo thoms...@gmail.com wrote: Hello, I register my domains at Dreamhost. I have an application on Heroku and I am trying to use a custom domain. I have added the domain, both root and www to the application and also added the three A type records and the www CNAME record at Dreamhost. My NS type records still point to ns#.dreamhost.com. The domain still does not direct to the application and I get a server cannot be found in my browser. Has anybody successfully pointed a Dreamhost domain to their Heroku application? - Braxo -- 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. -- 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 DB import 1M+ rows?
If you have a dedicated database, you can use psql to read off the local filesystem. http://docs.heroku.com/heroku-postgresql#psql-console Alternatively, you can dump your data and then restore it. http://docs.heroku.com/pgbackups#import On Fri, Dec 10, 2010 at 10:51 AM, Zach Bailey znbai...@gmail.com wrote: Thanks John, that's a great suggestion. Unfortunately it's looking like it will take about 7.5 hours to import 3.12M rows: 1 tables, 3,123,800 records companies: 1% | | ETA: 07:25:34 I'm wondering if there's a more expedient route... in the past I've used the postgres COPY command [1] to do bulk imports of large data sets quickly, but that requires that the server be able to read a file off the server's local filesystem. I don't suppose that's feasible given how the Heroku platform works, but would love to be pleasantly surprised :) Anyone from Heroku able to pipe up and offer any other possible suggestions? Just to restate the problem, I have a single table with about 3.12M records that I'm wanting to transfer from a local DB to my remote Heroku DB without touching the other Heroku app data. It's ok if the table gets blown away on the Heroku side as it has nothing in it (new model I just added). Happy Friday, Zach [1] http://www.postgresql.org/docs/8.4/interactive/sql-copy.html On Thursday, December 9, 2010 at 4:36 AM, johnb wrote: If it's just a single table and you have it in a db locally then db:push --tables tablename would get it up to heroku - but this will replace the contents of the remote table with the local table and not append to it. If the application is live you could put it into maintenance mode, db:pull --tables tablename append your rows to it and then push the table back and put the app live... perhaps? John. -- 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. -- 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. -- 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 / rails 2.3.5 - wrongly looking for dev gems in production
Barry, You have a space in your config var. You need to use a : $ heroku config:add BUNDLE_WITHOUT=development:test Oren On Mon, Nov 22, 2010 at 3:23 PM, Barry Hoggard ba...@tristanmedia.com wrote: I'm not sure what you're asking? I have this all working fine on a 3.0 Rails app, but for this 2.3.4 one, it's trying to load my dev gems when the app starts up on Heroku even thought the Rails environment is production. I would prefer not to go back to the manifest approach if I can help it. On Nov 22, 5:37 pm, Steve Smith st...@scsworld.co.uk wrote: Hey Barry does bundle without development:test work for you? I had a similar issue and the heroku guys showed me this fix. This is the new bundler syntax anyway I just hadn't gotten around to changing it. -- 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. -- 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: User White Label
you need to register the domain with Heroku, and have the user setup their DNS to point to Heroku. e.g. either run heroku domains:add www.mydomain.com for each domain, or do that via api (look at the source to the gem to see the API call). You need to tell Heroku about each and every domain so we know how to route the traffic. Many sites do this - for example getcloudapp.com has this feature. Oren On Wed, Nov 17, 2010 at 8:04 PM, Alfie cityb...@gmail.com wrote: I'd like to be able to offer my users a white label version of our product, meaning that their account page can be accessed from their personal domain rather than from our site so... www.myapp.com/users/account/1 can be accessed directly at... www.myusersdomain.com _without_ an iframe or generic forwarding. My first thought was to give users a subdomain and then have them use a CNAME to point their personal domain to their subdomain on my app but that doesn't seem to work (I get a Heroku error page that says Heroku No Such App). There has to be an easier way to do what I want to do right? -- 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: I added BUNDLE_WITHOUT=development test, but Heroku still installs everything
Bundlr 1.0.3 changed the syntax for without. We are deploying a hotfix tomorrow. In the meantime, seperate the groups you don't want deployed with a : instead of a space. e.g. heroku config:add BUNDLER_WITHUOUT=development:test Oren On Mon, Nov 8, 2010 at 12:03 PM, Chris Hanks christopher.m.ha...@gmail.com wrote: Yes, this started happening for me on Friday (worked fine up until then). and it looks like it's still going on. When I push I see Using --without development test, but it tries to install all the development/test gems anyway (which it can't, for me, because Heroku can't handle ruby-debug19). I haven't had a burning need to deploy recently, so I've been waiting for Heroku to sort it out, but it looks like they haven't, yet. Anyway, it's definitely a bug, so why not open a support ticket about it? And maybe let us know how it works out? On Nov 6, 3:06 pm, Volkan Unsal spockspla...@gmail.com wrote: I wanted Heroku's bundler to ignore some gems I have installed. It doesn't manage to do that, and as a result I am getting lots of errors. -- 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. -- 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: App Timeouts
I've seen a few people with weird timeouts where the app owner was able to find out that it was a bug in their code. Anything from a weird SQL query locking a table that was hanging their process to API requests to other hard to track stuff. This gem (http://github.com/kch/rack-timeout) will timeout your requests after a period you specify. The advantage of this is you can set it to a short time, and exceptional/hoptoad should catch the timeout giving you some indication in the backtrace of what's going on. Oren On Fri, Nov 5, 2010 at 9:06 AM, Subbu Sastry sss.li...@gmail.com wrote: Has anyone found a reasonable solution to this problem yet? On our app as well, we notice totally random timeout errors that couldn't possibly be associated with db lookup -- sometimes request time out on pages that lookup a row by primary key on a table with 15 records. Favicon.ico timed out as well. The timeouts seem arbitrary, and *always* get fixed on server restart (heroku restart). This has happened to us a few times over the last week. And yes, as several of you have noted, there is no exceptions raised (neither exceptional nor NewRelic). I think given that we experienced timeout with favicon.ico and an about page with a single db lookup and newrelic doesn't see this at all, I suspect this is something higher up the heroku stack that is timing out .. It almost smells like a memory leak somewhere which is how app restart seems to fix the problem. Now, the question is whether the memory leak is in our app or somewhere else (plugins, gems, interaction with heroku stack) ... I will debug this, but wanted to see if someone else has found a reasonable solution to this. Subbu. On Oct 6, 9:37 pm, mattsly matt...@gmail.com wrote: In just manual testing my app, I've seen a fair number of timeouts (maybe a dozen) but have not received any communication. I am pretty sure I'd have no idea they occurred had I not personally witnessed the error page. I find this a borderline ship blocker for a migration to Heroku as I consider migrating a ~500K monthly page view app to Heroku, and get very anxious thinking about lots of users seeing funky error page and having no way of being alerted or knowing how prevalent the issue is. WRT to the timeouts, it's maybe 1% of requests thattimeout...and I still can't pin down why they're happening. I'm on a single dyno, with Koi, and 5 alpha testers on it concurrently (andtimeout errors are related to response...not concurrency...) and these are extremely simple paging requests, that according to New Relic, return in ~100MS on average...and then all of a sudden...bam! - a requesttimeout. And we're talking about essentially the exact same code path, except a different :offset in the ActiveRecord find call. The complexity is nothing along the lines of suggestedtimeoutcauses here:http://docs.heroku.com/performance#request-timeout Strangely, I just tried turning off all varnish level caching (which I hope to rely on heavily) to try and isolate the issue and now perf seems *more* consistent and faster (haven't seen a timout yet). Could it be that the timeouts are being caused during lookup at the Varnish layer? My understanding is this wouldn't be a possible explanation, as I think the dyno doesn't even catch a request if the a varnish cache hit is found. So maybe Varnish caching is a red herring...but does seem curious. Matt On Sep 24, 7:56 pm, John Norman j...@7fff.com wrote: Well, you should get an e-mail if your app is generating backlogs. I have one app that did generate 2 in a whole week, and I received at least two e-mails from Heroku suggesting that I up the number of dynos. On Fri, Sep 24, 2010 at 11:42 AM, mattsly matt...@gmail.com wrote: How are you finding the timeouts? Just manually? I was havingtimeout issues (that I now think I've solved - see below) but am concerned that, once I flip my site public, that: a) There's no apparent native reporting/alerting for timeouts or backlog too deep errors if they do occur b) No ability to render a custom (static) error page in that case Re: reporting. When timeouts occur, am I mistaken in not seeing them reported anywhere? They don't seem to throw exceptional or new relic exceptions with the free version? It's unclear to me that they would be with the (expensive - .$.05/hr = $36/month for alerting?) Silver - can anyone confirm that they in fact do? It seems liketimeout/backlog too deep reporting/alerting should really be a built-in feature of Heroku, since they are core elements in the architecture, and such alerting (especially backlog) helps you make a quick call about cranking dyno count up/down and or restarting an app to minimize adverse user affects...i.e. really what this cloud and hosting-as-a-service thing is all about. I'm about to (I think) migrate a high traffic site to Heroku. I *love* the idea of
Re: Sendgrid questions
If you exceed the quota with the add-on, sendgrid will start giving you authentication errors. To access the web interface, run heroku config grab the username/password, and login to sendgrid. Oren On Fri, Oct 29, 2010 at 12:09 PM, Russell Quinn m...@russellquinn.com wrote: * What happens if I exceed my quota? * How do we access the Sendgrid web interface from our Heroku account? -- 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. -- 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 routing issues
Paste the full output of your output from when you run it locally in production mode into a gist (gist.github.com) and paste that here. Oren On Fri, Oct 29, 2010 at 2:40 PM, Cris cristinarand...@gmail.com wrote: Hi there, thanks for the reply. The actions are defined in index of ApplicationController. There is no error message, simply that the code within index is not invoked. I ran in production mode locally, and it indeed gives the same error. I checked the routes and they are the same, after running rake routes. Also I'm running rails 2.3.8 It doesn't appear that code should be used in the index method of Action Controller... On Oct 29, 4:00 pm, Chris Hanks christopher.m.ha...@gmail.com wrote: Can you explain what is actually happening? Is there an error message? Also, actions aren't typically defined in the ApplicationController, so I wouldn't be surprised if putting them there makes things iffy. You can try running your app in production mode on your local machine is order to see whether the problem is the environment or Heroku (try rails s production at the command line). On Oct 29, 12:33 pm, Cris cristinarand...@gmail.com wrote: I should have also added the routing problems occur in the production environment (on heroku) but not in dev environment. Thanks On Oct 29, 2:15 pm, Cris cristinarand...@gmail.com wrote: Hi there, I'm having problems with routing in my heroku environment heroku. I have this redirect in the index method of the application controller. class ApplicationController ActionController::Base . def index redirect_to root_url end end this works perfectly in my local environment yet in heroku it fails (does not get redirectly). All other routing is functioning correctly, all except for the index method of ApplicationController. Is there something that is causing this in the heroku environment that I have overlooked? Thanks in advance, I'm new to the heroku environment. Thanks, Cris -- 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. -- 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.
Postmortem on Tuesday's outage
We have posted a postmortem on Tuesday's outage on our blog: http://blog.heroku.com/archives/2010/10/27/tuesday_postmortem/ 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 at http://groups.google.com/group/heroku?hl=en.
Re: Sinatra 1.1
Simply put it in your .gems or Gemfile and you'll be all set. Oren On Tue, Oct 26, 2010 at 5:58 AM, DAZ daz4...@gmail.com wrote: Hi, Sinatra upgraded to version 1.1 yesterday. Is this version available on Heroku and how do I update current apps that are using Sinatra to the new version? cheers, DAZ -- 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. -- 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: Unable to push application..
http://status.heroku.com is the first place to check. We had a brief git push outage yesterday. Oren On Tue, Oct 26, 2010 at 12:07 AM, Hemal Kuntawala hemal.kuntaw...@gmail.com wrote: I got notifications around this time that just pinging our app took ages - might be a heroku thing. Tried this morning? On 26 October 2010 02:42, WilliamF wflana...@tempusgroup.com wrote: Hi all, Heroku is failing on launch with a Launching. failed (Heroku error) message. Any ideas how to fix? Anyone else having this problem? William -- 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. -- 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. -- 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: Sinatra 1.1
By not specifiying a gem version we will always pull the latest version when you change your .gems/gemfile. This is a bad idea however, as your app could randomly break if for example sinatra 2.0 comes out and changes an API you depend on. Oren On Tue, Oct 26, 2010 at 11:35 AM, DAZ daz4...@gmail.com wrote: Thanks Oren, I changed my .gems file to say sinatra --version 1.1 instead of just sinatra Is there any way of forcing Heroku to always go and look for the latest gems without having to specify a version number? cheers, DAZ On Oct 26, 4:30 pm, Oren Teich o...@heroku.com wrote: Simply put it in your .gems or Gemfile and you'll be all set. Oren On Tue, Oct 26, 2010 at 5:58 AM, DAZ daz4...@gmail.com wrote: Hi, Sinatra upgraded to version 1.1 yesterday. Is this version available on Heroku and how do I update current apps that are using Sinatra to the new version? cheers, DAZ -- 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. -- 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: Sinatra 1.1
Both are correct. Just add a blank line and we'll pull the latest version if you havn't specified. Best practice is to pin all versions to prevent nasty surprises. Oren On Tue, Oct 26, 2010 at 11:53 AM, DAZ daz4...@gmail.com wrote: thanks Oren, I've tested it locally, so was happy to update. So would I have to just change the .gems file with something trivial to 'force' an update? Or are you saying that best practice is to always specify version numbers? cheers, DAZ On Oct 26, 7:40 pm, Oren Teich o...@heroku.com wrote: By not specifiying a gem version we will always pull the latest version when you change your .gems/gemfile. This is a bad idea however, as your app could randomly break if for example sinatra 2.0 comes out and changes an API you depend on. Oren On Tue, Oct 26, 2010 at 11:35 AM, DAZ daz4...@gmail.com wrote: Thanks Oren, I changed my .gems file to say sinatra --version 1.1 instead of just sinatra Is there any way of forcing Heroku to always go and look for the latest gems without having to specify a version number? cheers, DAZ On Oct 26, 4:30 pm, Oren Teich o...@heroku.com wrote: Simply put it in your .gems or Gemfile and you'll be all set. Oren On Tue, Oct 26, 2010 at 5:58 AM, DAZ daz4...@gmail.com wrote: Hi, Sinatra upgraded to version 1.1 yesterday. Is this version available on Heroku and how do I update current apps that are using Sinatra to the new version? cheers, DAZ -- 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 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. -- 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: Outbound IP address
To have outbound traffic come from a single IP you need to setup a 3rd party proxy, either on your own EC2 instance or using a 3rd party proxy provider. Oren On Fri, Oct 22, 2010 at 1:25 PM, Mike Doel m...@mikedoel.com wrote: I imagine this is in TFM somewhere, but my google skills are failing me. If we have paid for the custom SSL package, will traffic outbound from our app have the IP address assigned to us in that process? Alternatively, is there a netmask that can be counted on for outbound traffic? Our app needs to access a third party gateway that is using IP address as one of the parameters in controlling access. Mike -- 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: heroku_user
That article references our old Heroku Garden platform. The current platform is based on standards, so your best bet is to use one of the libraries mentioned like Devise. Oren On Sun, Oct 24, 2010 at 1:34 PM, Abel Tamayo abel.tam...@gmail.com wrote: It looks like Heroku Users are used to authenticate users who already have an account with Heroku and are allowed to check out the application's source (that's the impression I get from skimming through the article). If you're looking for a commonly used, standard authentication method, Authlogic and Devise seem to be the most commonly used gems for the task. You can find tutorials on them both at railscasts.com On Thu, Oct 21, 2010 at 10:28 AM, jundai bates.kobashig...@gmail.comwrote: Hello, In looking for a dead-simple auth option for my heroku app, I noticed this page: http://blog.heroku.com/archives/2008/1/14/heroku_user/ I tried accessing heroku, and I wasn't able to get it working. I get a: NameError (undefined local variable or method `heroku_user' for #FilmViewingsController:0x2b17f842faa0): app/controllers/application_controller.rb:6:in `authorized?' app/controllers/film_viewings_controller.rb:39:in `edit' Is heroku_user something that's still available within heroku apps? Is there anything I have to do to enable it? Is it called something else now? I can't seem to find any indication that it's been removed as a feature, though I imagine heroku's platform has seen a lot of change since 2008. -Jdbk -- 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.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: Unable to install the fancybox rails plugin on heroku
heroku plugins:install is for installing heroku client plugins. You want to use rails plugin install instead. Oren On Wed, Oct 13, 2010 at 9:57 PM, vishy shubhambansa...@gmail.com wrote: I am trying to install the plugin on a heroku app. The command heroku plugins:install git://github.com/vanntastic/fancy_box_rails_plugin.git runs fine. But when I try to run the command heroku rake fancy_box:install, I get an exception - Unable to load plugin: some_plugin: uninitialized constant FancyBox::Constants rake aborted! Read-only file system - /disk1/home/slugs/278841_72b0cfa_4d5e/mnt/ public/stylesheets/jquery.fancybox.css (See full trace by running task with --trace) (in /disk1/home/slugs/ 278841_72b0cfa_4d5e/mnt) Also whenever I would run the command heroku plugins, I would again get this Unable to load plugin: some_plugin: uninitialized constant FancyBox::Constants fancy_box_rails_plugin Any help regarding this will be greatly appreciated. I am using rails 3.0 with ruby 1.9.2. Thanks, -- 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: Is there a maximum /tmp tempfile size?
The file size limit is in the many gigs range. Clean up after yourself and you shouldn't have any problems. Workers are capped at the same memory limit. Oren On Tue, Oct 5, 2010 at 7:11 PM, mdgbayly martin.ba...@gmail.com wrote: I have a background job running as a worker that needs to generate and write large files to s3. From what I can tell s3 doesn't support chunked transfer encoding so I need to know the size of the file before I can start writing it to s3. One option is to write the file to memory before putting to s3 but as these files could be quite bit, that could chew up a lot of memory. The other option is to write it to a temp file under my application root /tmp directory, and then upload the temp file to s3 from there. I've read the info at http://docs.heroku.com/constraints#read-only-filesystem and realize that the files won't hang around if my worker is stopped restarted etc, but that's ok. I'd just be generating it, uploading to s3 and then deleting the local copy. I've also read that there is a 300MB hard memory cap for dynos? Is that true for workers too? Cheers Martin -- 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. -- 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 Mongoid config and how it works
Nope - the only thing an add-on does is set one config var -
MONOGHQ_URL in this case. No other magic. Some add-ons like new
relic will also install a gem or plugin, but mongo hq isn't one of
them. Those are the only actions an add-on can take.
Oren
On Wed, Sep 29, 2010 at 7:55 PM, Bradley bradleyrobert...@gmail.com wrote:
It's interesting, after searching through the source of the gem,
there's a mongoid.yml in a generator that references the same env vars
for the db connection (MONGOID_HOST, MONGOID_PORT... etc), and yet I
don't see the gem creating these anywhere. So I'm still confused as
to where these were generated. It MUST be part of heroku in some
way... no? maybe the mongohq addon?
On Sep 27, 11:47 am, John Barnette jbarne...@gmail.com wrote:
On Sep 27, 2010, at 8:44 AM, Chris Hanks wrote:
On Sep 27, 6:51 am, Abel Tamayo abel.tam...@gmail.com wrote:
It seems MongoMapper is more popular around here. At least it's the
solution
I'm using and works flawlessly with Heroku.
On Mon, Sep 27, 2010 at 2:33 PM, Bradley bradleyrobert...@gmail.com
wrote:
no one has a comment on this? I thought it'd be a fairly straight
forward answer.
Why bother with the YML file?
require mongoid
require uri
url = URI.parse ENV[MONGODB_URL]
MONGO = Mongo::Connection.new(url.host, url.port).db url.path[1..-1]
if url.user url.password
unless MONGO.authenticate url.user, url.password
raise Couldn't authenticate MongoDB: #{url.to_s}
end
end
Mongoid.configure do |config|
config.autocreate_indexes = true
config.master = MONGO
config.persist_in_safe_mode = false
config.raise_not_found_error = false
end
--
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.
--
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 Mongoid config and how it works
I'm not sure what's going on, but Heroku doesn't do any magic like that. When you add the mongohq addon, the only url that is set is the MONGOHQ_URL. I just tested it on one of my apps, added mongohq, and there is nothing set for MONGOID_*. Perhaps that's a feature that the mongoid gem itself provides? Oren On Mon, Sep 27, 2010 at 5:43 PM, Chris Hanks christopher.m.ha...@gmail.com wrote: I guess they wanted the MongoHQ addon to just work with Mongoid in addition to MongoMapper. On Sep 27, 4:58 pm, Bradley bradleyrobert...@gmail.com wrote: ya you're right, those env vars exist. i wonder why the docs on this are so sparse, and how the author of this template found this out. I haven't been able to locate anything that gives an indication that this is happening. On Sep 27, 11:44 am, Chris Hanks christopher.m.ha...@gmail.com wrote: Heroku might be breaking up the ENV['MONGOHQ_URL'] into those components for you. Try heroku console from your command line and then ENV['MONGOID_HOST'] to see if it's present. On Sep 27, 6:51 am, Abel Tamayo abel.tam...@gmail.com wrote: It seems MongoMapper is more popular around here. At least it's the solution I'm using and works flawlessly with Heroku. On Mon, Sep 27, 2010 at 2:33 PM, Bradley bradleyrobert...@gmail.com wrote: no one has a comment on this? I thought it'd be a fairly straight forward answer. On Sep 22, 7:11 pm, Bradley bradleyrobert...@gmail.com wrote: I just used a template for a new rails app that sets up everything for use with Mongoid. The mongoid.yml file looks like this: production: host: %= ENV['MONGOID_HOST'] % port: %= ENV['MONGOID_PORT'] % username: %= ENV['MONGOID_USERNAME'] % password: %= ENV['MONGOID_PASSWORD'] % database: %= ENV['MONGOID_DATABASE'] % I added the MONGOHQ_URL config var to my app (with the string given from mongohq), deployed and it worked! My question is... HOW? I don't get how adding that single URL has all of a sudden given me these 5 environment variables. I searched through the heroku docs on mongo and they pretty sparse. Nowhere does it mention that I might use these particular env vars. So how does this happen? -- 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. -- 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: Image upload - manipulation - copy to S3
1) With Heroku I understand your request can have some temporary space for file uploads. Can I rely on that space to exist for a few minutes while a Delayed Job gets to it? The space is for the request. A delayed job will run as a seperate process, so no, you can't count on it being there. Chances are high that the delayed job will run on a different machine, and not have access to the file. Note that for small files, you can have the dyno upload to s3 as part of the process. Paperclip supports this out of the box. I have sites myself working this way. 2) Does uploading a file completely lock a dyno? Or can a single dyno handle a few simultaneous uploads? A dyno is by definition one simultaneous request. That dyno is locked for the duration of the upload. 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 at http://groups.google.com/group/heroku?hl=en.
Re: upload size limit?
There is no hard limit - it's all the same 30 second time limit. No request can take 30 seconds. Oren On Fri, Sep 24, 2010 at 8:12 AM, marcel mpoi...@gmail.com wrote: 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. -- 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: Caching of /public files
Heroku by default caches all static assets in /public for 24 hours. Oren On Wed, Sep 22, 2010 at 3:39 AM, Alex a...@heaton.me wrote: Sorry, I should have specified, the files stored in /public on rails for instance. These aren't managed by a controller (so no headers that way) and I was wondering if heroku had a default approach to them. It occurs to me that this may be entirely a Rack issue, though hopefully somebody here can point me in the right direction. On Sep 22, 4:01 am, Jeff Deville jeffdevi...@gmail.com wrote: This what you're looking for?http://docs.heroku.com/http-caching On Tue, Sep 21, 2010 at 10:36 PM, Alex a...@heaton.me wrote: I'm wondering about the options for caching of public files, I would image they are cached by default? How do you set caching headers on them for instance? -- 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. -- 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: Caching of /public files
The docs are right - I was wrong. We cache for 12 hours. Oren On Wed, Sep 22, 2010 at 5:17 PM, Keenan Brock kee...@thebrocks.net wrote: I could have sworn it was 24. But the documentation said 12... http://docs.heroku.com/http-caching What is the best channel to request an update to the docs? --Keenan On Sep 22, 2010, at 3:08 PM, Oren Teich o...@heroku.com wrote: Heroku by default caches all static assets in /public for 24 hours. Oren On Wed, Sep 22, 2010 at 3:39 AM, Alex a...@heaton.me wrote: Sorry, I should have specified, the files stored in /public on rails for instance. These aren't managed by a controller (so no headers that way) and I was wondering if heroku had a default approach to them. It occurs to me that this may be entirely a Rack issue, though hopefully somebody here can point me in the right direction. On Sep 22, 4:01 am, Jeff Deville jeffdevi...@gmail.com wrote: This what you're looking for?http://docs.heroku.com/http-caching On Tue, Sep 21, 2010 at 10:36 PM, Alex a...@heaton.me wrote: I'm wondering about the options for caching of public files, I would image they are cached by default? How do you set caching headers on them for instance? -- 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. -- 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. -- 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. -- 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: Zerigo MX records and GoDaddy Forwarders
I'm not entirely clear on what you're trying to do. Are you looking for someplace to host email. e.g. you want f...@mydomain.com to go somewhere, and provide webmail/pop/imap type functionality? If yes, google apps for domains is the best way to go . Oren On Sat, Sep 18, 2010 at 10:31 AM, Octopus Inc octopus...@me.com wrote: Can someone help me connect my app that is using Zerigo to some email forwarders I've set up on GoDaddy? The MX entries I have now are: @ : smtp.secureserver.net @ : mailstore1.secureserver.net --- I just signed up for Heroku, and I love it. I'm an old cPanel user and I never really used anything else besides Add-on Domains, Subdomains, Redirects, Email, Forwarders (thank goodness Rails slayed phpMyAdmin). I'm trying not to get GoDaddy or Google involved in my apps email, and the screencasts only cover the custom domains addon. How would I simply set up email forwarders using Sendgrid Zerigo, or is that even possible. It looks like Zerigo specializes in what GoDaddy would call TotalDNS and Sendgrid specializes in outbound email only. Could I still use GoDaddy email services if I pointed the DNS at Zerigo and then use Sendgrid strictly for app generated email? -- 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. -- 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: wonderful platform for app staging...
The docs are cloneable. Edit away, and send a pull request. We're happy to incorporate great ideas! http://github.com/heroku/heroku-docs Oren On Mon, Sep 20, 2010 at 5:32 PM, Roy Wang dinoro...@gmail.com wrote: Yes, GitHub+Heroku is fantastic. If only Heroku had better documentation... Is there a wiki for Heroku? Roy On Tue, Sep 21, 2010 at 8:07 AM, Dennis dennismaj...@gmail.com wrote: I believe Rails 3 works with Ruby 1.8.7: http://edgeguides.rubyonrails.org/getting_started.html I think it is only a couple of p releases of 1.8.7 that cause problems (see above link) ... later versions of 1.8.7 are available - for windows at least and I think archived versions of 1.8.7 would be available for other OS's On Sep 19, 1:26 pm, kadoudal kadou...@gmail.com wrote: I subscribed recently to Heroku and found how easy it is (together with GitHub) to deploy apps and test them 'live' HOWEVER all new Rails applications are to be designed with the pair Rails3-Ruby1.9.2 as they have been released unfortunately Heroku does support Rails3 only with Ruby 1.8.7 at the present time... and I have to go back to my old staging deployment environment... I hope they will support 1.9.2 asap , any idea of when this could happen ?? matter of weeks.. months.. quarters.. hungry now ... -- 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. -- 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. -- 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: Error when using memcached uninitialized constant Memcached (NameError)
if you're using a gemfile, you don't want to have any config.gem directives. It's one or the other. Bundler replaces the way rails 2.3 handles gems. http://gembundler.com/rails23.html http://gembundler.com/rails23.htmlif oyu're using bundler, it's gem memcached-northscale, :require = memcache Oren On Fri, Sep 10, 2010 at 4:15 AM, riton enjoy...@gmail.com wrote: Hello, I added the memcache 5MB free addon to my application. I'm trying to make it work using the northscale gem as specified in the documentation. I can't make it to work. I can't get past this error /production.rb:33: uninitialized constant Memcached (NameError) Here is my Gemfile: gem 'memcache-client' gem 'memcached-northscale' my environment.rb: # Load memcached config.gem 'memcached-northscale', :lib = 'memcached' require 'memcached' my production.rb: config.cache_store = :mem_cache_store, Memcached::Rails.new Despite your documentation saying to remove memcache-client from the Gemfile, (I tried..) some guys seem to say we need it (ex: http://github.com/heroku-examples/r3b4-memcache-heroku/commit/f10e62d3d71dea664c090a2e28fe7619d3b6a62d ) Well, I'm not sure what I should do. Here is an EVENT_ID i'm getting (sometime) on my app when trying to reach it (error 503), maybe it's related ? Event ID: 05040001c8a60003714f Thanks for helping me out ! -- 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: Error when using memcached uninitialized constant Memcached (NameError)
I missed the last d. gem memcached-northscale, :require = memcached On Fri, Sep 10, 2010 at 3:38 PM, riton enjoy...@gmail.com wrote: hi Oren, Thanks for looking into my issue. Here are the modifications I made to my app , according to the heroku documentation and what you just said. Please, can you tell me what's wrong in that: environment.rb: no changes. I don't have to add the 'config gem' and 'require' lines environment/production.rb: added config.cache_store = :mem_cache_store, Memcached::Rails.new Gemfile: gem memcached-northscale, :require = memcache Is that correct ? If no, do i need gem 'memcache' in my Gemfile ? I tried with it, and with gem 'memcached' but without success. I ran bundle install in my local installation, my gemfile.lock is in GIT and this is fine with heroku's bundle (it runs whenever I add a gem in Gemfile). Here are the gem used with bundle Using rake (0.8.7) Using abstract (1.0.0) Using activesupport (3.0.0.rc2) Using builder (2.1.2) Using i18n (0.4.1) Using activemodel (3.0.0.rc2) Using erubis (2.6.6) Using rack (1.2.1) Using rack-mount (0.6.13) Using rack-test (0.5.4) Using tzinfo (0.3.23) Using actionpack (3.0.0.rc2) Using mime-types (1.16) Using polyglot (0.3.1) Using treetop (1.4.8) Using mail (2.2.5) Using actionmailer (3.0.0.rc2) Using arel (1.0.1) Using activerecord (3.0.0.rc2) Using activeresource (3.0.0.rc2) Using memcache (1.2.13) Using memcached-northscale (0.19.5.4) Using mysql (2.8.1) Using mysql2 (0.2.3) Using bundler (1.0.0) Using thor (0.14.0) Using railties (3.0.0.rc2) Using rails (3.0.0.rc2) And the error: /disk1/home/slugs/283964_74b4131_849c/mnt/config/environments/ production.rb:33: uninitialized constant Memcached (NameError) Sorry, I don't know what to do . On Sep 10, 5:54 pm, Oren Teich o...@heroku.com wrote: if you're using a gemfile, you don't want to have any config.gem directives. It's one or the other. Bundler replaces the way rails 2.3 handles gems. http://gembundler.com/rails23.html http://gembundler.com/rails23.htmlif oyu're using bundler, it's gem memcached-northscale, :require = memcache Oren On Fri, Sep 10, 2010 at 4:15 AM, riton enjoy...@gmail.com wrote: Hello, I added the memcache 5MB free addon to my application. I'm trying to make it work using the northscale gem as specified in the documentation. I can't make it to work. I can't get past this error /production.rb:33: uninitialized constant Memcached (NameError) Here is my Gemfile: gem 'memcache-client' gem 'memcached-northscale' my environment.rb: # Load memcached config.gem 'memcached-northscale', :lib = 'memcached' require 'memcached' my production.rb: config.cache_store = :mem_cache_store, Memcached::Rails.new Despite your documentation saying to remove memcache-client from the Gemfile, (I tried..) some guys seem to say we need it (ex: http://github.com/heroku-examples/r3b4-memcache-heroku/commit/f10e62d. .. ) Well, I'm not sure what I should do. Here is an EVENT_ID i'm getting (sometime) on my app when trying to reach it (error 503), maybe it's related ? Event ID: 05040001c8a60003714f Thanks for helping me out ! -- 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.
Re: SSH Keys
You need to add your keys from the command line with the heroku gem: heroku keys:add Oren On Wed, Sep 8, 2010 at 11:13 AM, Steven Garcia stevendgar...@gmail.comwrote: When I am added as a collaborator to a project I am unable to push or clone due to an error Permission denied (publickey). This is a bit confusing for me since there is no way to add my own ssh key in heroku's control panel. I've checked the documentation and have done everything by the book, first trying to clone the link sent to my email and then also trying to init a blank repo and adding the remote repo to my .git/config Nothing seems to work. Any one know how to do this? (or why heroku doesnt provide key management in the web app)? -- 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: How to deploy app with sensitive config information?
thanks for the note - docs updated. Oren On Fri, Sep 3, 2010 at 1:22 PM, marcel mpoi...@gmail.com wrote: 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.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: free vs. paid heroku app performance
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 Slug compile should never take that long. It sounds like a bug - we have noticed a few stale lock files on compiles. We're digging in to see what's going on over the next few weeks on this particular area. For the sake of clarity (and a future docs page I'll put up): h1. When do you idle my app? Only dynos are idled, not workers. If you have only 1 free dyno, your app will be spun down after a period of inactivity. This period is variable depending on demand on the platform, but is never less than 20 minutes or more than 1 hour. No other resources are different. Git push, slug compilation, etc are all identical. Increasing your dyno to 1 will prevent your app from idling out. Note: other resources (workers, add-ons) do not effect dyno idling at this time. If you have 1 dyno + 10 workers, your dyno will still idle out after a period of inactivity. We never idle out workers. What other questions do you guys have on the area that I should include? 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 at http://groups.google.com/group/heroku?hl=en.
Re: free vs. paid heroku app performance
What is Heroku's timeout when spinning up dynos/workers? I thought that I'd seen this mentioned somewhere, but I can't find it now. I ask because an app I'm thinking of would need to hit external services and the database when starting up, which could take a while. 30 seconds. Is there a limit to how long a daily cron job can run? I'm planning on some number crunching that could take up to an hour or so. You should aim for a few seconds, minute at most. If you need that long a job, you should be using a worker to run it. 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 at http://groups.google.com/group/heroku?hl=en.
Re: EU bucket cost implications
We are in US-EAST. On Thu, Aug 19, 2010 at 3:50 AM, Alex a...@heaton.me wrote: I don't actually know which of the locations Heroku runs from, perhaps someone from heroku can help us out. -- 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: NOTICE: Updating Bundler this week
Bundler 1.0.0 RC2 is now deployed. On Sunday, August 1, 2010, Oren Teich o...@heroku.com wrote: On Tuesday August 3rd we will be updating Bundler to 1.0.0RC2. Apps will continue to run unaffected. Before you push an update, please double check that your app works correctly with the latest version of Bundler. Some things to note: * Adding an add-on or a config var will recompile your application. This can crash your application if you haven't tested it. Please test against Bundler 1.0.0RC2 before modifying your application. * Run bundle check locally with Bundler 1.0.0RC2 installed * Are you bundling Bundler? Check your Gemfile to see if you list Bundler, and have pinned the version. Bundler can't bundle an older version of itself. We will roll the update out mid-day Tuesday August 3rd. 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 at http://groups.google.com/group/heroku?hl=en.
Re: NOTICE: Updating Bundler this week
We've delayed the update till tomorrow due to platform issues today. http://status.heroku.com Oren On Tue, Aug 3, 2010 at 5:29 PM, Solly directxma...@gmail.com wrote: Hi - How is the upgrade going? Not to pester, but Heroku's Bundler still appears to be the old version. Even in CA, it is past mid-day. Are you having some problems? I don't mean to push; I am just eager to push an updated version of my app to Heroku, as I have done some major revisions during the past few days. Best Regards, Solly Ross P.S. I understand that upgrades can easily turn nasty -- I'm just interested in a status update ;-) On Aug 2, 12:33 am, Adrian Cuadros adrian.cuad...@gmail.com wrote: Great, Have been waiting a few days for this. Thanks :) On 1 ago, 20:29, Oren Teich o...@heroku.com wrote: On Tuesday August 3rd we will be updating Bundler to 1.0.0RC2. Apps will continue to run unaffected. Before you push an update, please double check that your app works correctly with the latest version of Bundler. Some things to note: * Adding an add-on or a config var will recompile your application. This can crash your application if you haven't tested it. Please test against Bundler 1.0.0RC2 before modifying your application. * Run bundle check locally with Bundler 1.0.0RC2 installed * Are you bundling Bundler? Check your Gemfile to see if you list Bundler, and have pinned the version. Bundler can't bundle an older version of itself. We will roll the update out mid-day Tuesday August 3rd. 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.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: Heroku console crashing
Also check out http://github.com/ddollar/heroku-sql-console On Mon, Aug 2, 2010 at 9:15 AM, Jonathan jse...@gmail.com wrote: Running database transactions through this remote console setup is iffy... It might work better to do a db:pull (ideally of just the tables you want to change), do the database maintenance locally, and then push the updated tables. You can put the site into maintenance mode while you do this, if necessary. This technique works reasonably well for me. On Aug 1, 6:44 pm, Mike mikel...@gmail.com wrote: I'm updating some data in my database, and running them through the Heroku console since we have no direct database access... -- 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. -- 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.
NOTICE: Updating Bundler this week
On Tuesday August 3rd we will be updating Bundler to 1.0.0RC2. Apps will continue to run unaffected. Before you push an update, please double check that your app works correctly with the latest version of Bundler. Some things to note: * Adding an add-on or a config var will recompile your application. This can crash your application if you haven't tested it. Please test against Bundler 1.0.0RC2 before modifying your application. * Run bundle check locally with Bundler 1.0.0RC2 installed * Are you bundling Bundler? Check your Gemfile to see if you list Bundler, and have pinned the version. Bundler can't bundle an older version of itself. We will roll the update out mid-day Tuesday August 3rd. 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 at http://groups.google.com/group/heroku?hl=en.
Re: Heroku console crashing
That's how Heroku works - http://docs.heroku.com/performance#request-timeout. A console command is treated identically to a HTTP request. Oren On Sun, Aug 1, 2010 at 6:57 PM, Mike mikel...@gmail.com wrote: Okay, actually fixed this, sort of, by updating my heroku gem. Now it now longer crashes and just quits the console and tells me that it's timed out and I should run it as a rake task instead of from the console. Overall behavior seems to be the same still, with the request continuing to run on the dyno until completed. On Aug 1, 9:44 pm, Mike mikel...@gmail.com wrote: I'm updating some data in my database, and running them through the Heroku console since we have no direct database access. I'm calling this like so: ActiveRecord::Base.connection.execute MY SQL COMMAND; The command takes about 5-10 minutes to run. Every time I run it, it's causing the console to crash, with the following message: /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/client.rb:202:in `console': undefined method `code' for nil:NilClass (NoMethodError) from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/commands/app.rb: 158:in `console_session' from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/commands/app.rb: 147:in `console' from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/command.rb:48:in `send' from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/command.rb:48:in `run_internal' from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/command.rb:20:in `run' from /var/lib/gems/1.8/gems/heroku-1.9.9/bin/heroku:13 from /var/lib/gems/1.8/bin/heroku:19:in `load' from /var/lib/gems/1.8/bin/heroku:19 After that, apparently the command is continuing to run even though I have no access to the console, as for about the runtime of my command, the dyno continues to be completely tied up and non-responsive. Afterwards, I can connect to the console again, and the data appears upon first inspection to have been changed. Has anyone else seen behavior like this? Did your data integrity turn out okay in the end? -- 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. -- 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 long are cron jobs allowed to run for?
There is no hard limit currently. I'd suggest you not have them run for more than a few minutes. If you need to do longer work, have the cron job fire off a background task. Oren On Sat, Jul 17, 2010 at 5:57 PM, GarethLAtWork garethlatw...@gmail.comwrote: Does Heroku kill off cron jobs after a certain length of time? -- 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: alternative to pony
Any reason you are trying to keep the slug size down? Anything under 50MB isn't a problem. Oren On Thu, Jul 8, 2010 at 1:27 PM, Shane sh...@digitalsanctum.com wrote: I just added pony to my app to send email and it added ~1.5MB to my slug size. Is there an alternative that's lighter? Thanks, Shane -- 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: Can't use memcache with my application
Just pushed an update for the northscale gem:
http://github.com/heroku-examples/r3b4-memcache-heroku/commit/4fbc4f15dfa9f375b30325a62d9311a87cf07e7b
Oren
On Fri, Jun 25, 2010 at 4:11 AM, Neil Middleton neil.middle...@gmail.comwrote:
I'm not sure if this is a related issue or not, but heroku have an example
app of Rails 3b4 with memcached here:
http://github.com/heroku-examples/r3b4-memcache-heroku
However, if we flip it to memcached-northscale we start seeing :
/Users/neil/Dropbox/code/r3b4-memcache-heroku/config/environments/production.rb:29:
uninitialized constant Memcached (NameError)
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:55:in
`class_eval'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:55:in
`configure'
from
/Users/neil/Dropbox/code/r3b4-memcache-heroku/config/environments/production.rb:1
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application/bootstrap.rb:10:in
`require'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application/bootstrap.rb:10
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:25:in
`instance_exec'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:25:in
`run'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:55:in
`run_initializers'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:54:in
`each'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:54:in
`run_initializers'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:119:in
`initialize!'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:81:in
`send'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:81:in
`method_missing'
from /Users/neil/Dropbox/code/r3b4-memcache-heroku/config/environment.rb:5
from config.ru:3:in `require'
from config.ru:3
from /Library/Ruby/Gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb:46:in
`instance_eval'
from /Library/Ruby/Gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb:46:in
`initialize'
from config.ru:1:in `new'
from config.ru:1
This might be a non-issue, but we thought it worth pointing out differences
between the two gems.
Neil
On Thu, Jun 24, 2010 at 5:39 PM, Sean Lynch se...@literati.org wrote:
Hi, Eki.
This is a side-effect of Fauna's throwing exceptions for errors that would
just show up as misses in memcache-client. I've fixed this and it's in
testing in a gem called memcached-northscale. You still use require
'Memcached', just use memcached-northscale instead of memcached in your
gem.
Once I get feedback that it a) solves the problem and b) doesn't cause
other problems, I'll get it incorporated into Fauna.
Thanks!
-Sean
On Jun 24, 2010, at 3:46 AM, Eki wrote:
Hi guys ,
I'm trying to use memcached with my application , I followed the
official instructions to do so but still not working ,
the error msg is something like this :
Memcached::ServerIsMarkedDead (Key
{country_x_y_z=127.0.0.1:11211:8}):
memcached (0.19.7) lib/memcached/memcached.rb:609:in
`check_return_code'
memcached (0.19.7) lib/memcached/memcached.rb:515:in `get'
memcached (0.19.7) lib/memcached/rails.rb:39:in `get'
app/controllers/prayer_times_controller.rb:9:in `index'
/home/heroku_rack/lib/static_assets.rb:9:in `call'
/home/heroku_rack/lib/last_access.rb:25:in `call'
/home/heroku_rack/lib/date_header.rb:14:in `call'
thin (1.0.1) lib/thin/connection.rb:80:in `pre_process'
thin (1.0.1) lib/thin/connection.rb:78:in `catch'
thin (1.0.1) lib/thin/connection.rb:78:in `pre_process'
thin (1.0.1) lib/thin/connection.rb:57:in `process'
thin (1.0.1) lib/thin/connection.rb:42:in `receive_data'
eventmachine (0.12.6) lib/eventmachine.rb:240:in `run_machine'
eventmachine (0.12.6) lib/eventmachine.rb:240:in `run'
thin (1.0.1) lib/thin/backends/base.rb:57:in `start'
thin (1.0.1) lib/thin/server.rb:150:in `start'
thin (1.0.1) lib/thin/controllers/controller.rb:80:in `start'
thin (1.0.1) lib/thin/runner.rb:173:in `send'
thin (1.0.1) lib/thin/runner.rb:173:in `run_command'
thin (1.0.1) lib/thin/runner.rb:139:in `run!'
thin (1.0.1) bin/thin:6
/usr/local/bin/thin:20:in `load'
/usr/local/bin/thin:20
Rendering /disk1/home/slugs/212292_698e4ed_e2ba/mnt/public/500.html
(500 Internal Server Error)
Any help will b highly appreciated .
Hope to hear from you soon guys .
Cheers
Eki
--
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
Re: git push heroku resets database each time
It's because you have your enviornment set. That's a rails feature. Production doesn't do that. On Fri, Jun 25, 2010 at 12:22 AM, lsiden lsi...@gmail.com wrote: Each time I push my app to heroku, I notice that the database has been reset (emptied). Is this because I have environment=test set? Or is it because my git refspec forces non-fast-forward pushes? Or is there some other reason that I don't know about. This could be a show-stopper when I deploy my app and it starts to gather real data. -- 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: Database importing very slow
Are you running the latest version of taps (sudo gem update taps)? Is the primary key on your table an integer? http://blog.heroku.com/archives/2010/4/21/supporting_big_data_part_1/ On Thu, Jun 24, 2010 at 4:25 AM, Brad oconnor.b...@gmail.com wrote: Oops, I didn't say how slow. So far it's been 2 hours. It looks like it'll be at least another hour. On Jun 24, 9:23 pm, Brad oconnor.b...@gmail.com wrote: I'm trying to upload my development database to my heroku app (via heroku db:push) but finding it very slow. My database is not huge - 11 tables, about 57000 records, 13MB diskspace but is taking hours to upload. I don't even know where to start with investigating this. The connection at my end is fine for any other activities. Surely heroku can't be this slow. -- 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: RMagick installation issues
Migrate your app to the bamboo stack - http://docs.heroku.com/bamboo On Thu, Jun 17, 2010 at 10:20 PM, rcanand rcan...@gmail.com wrote: Hi, I am relatively new to rails/heroku, so this may be a noob question. I am trying to deploy a rails 2.3.5 project to heroku. This project requires the RMagick gem v 2.13.1, which in turn requires ImageMagick. I tried to add a line to the .gems manifest for RMagick 2.13.1, and that line fails when I push my changes to heroku. The error states that ImageMagick 6.4.9 was required for RMagick, but not found. ImageMagick is not really a gem, and I dont know how to get this version onto the machine. I also noticed that the heroku default list has a different version of RMagick (1.15.17). I have tried running the same app on dev and on heroku, without adding rmagick to the gems manifest, and the app works locally, but fails in heroku. Thanks for your help! RCA -- 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: Rails 3 now 187 or 192 only
We won't be supporting 1.9.2head before 1.9.2 is officially released.We work hard to provide a stable platform for commercial deployment, and 1.9.2 isn't there yet. We are investigating updating 1.8.7 to the latest REE patch level to address the crashing 1.8.7 issue. Oren On Fri, Jun 11, 2010 at 2:27 PM, Yuri yuriga...@gmail.com wrote: After beta4, i.e., master for now, starting up with MRI 191 gets you this stick in the eye: Rails 3 requires Ruby 1.8.7 or 1.9.2. You're running 1.9.1 (2010-01-10); please upgrade to continue. And beta4 itself is pretty much a non-starter for 191 due to a 191- incompatible fix for multibyte chars, which ironically looks to be fixed in a compatible way for 191 in master now. But still, there it is. Any thoughts from Heroku on their beta Rails 3 / 191 option, i.e., possibility of 192 previews (realizing that's gotta be a pain to handle on your end, but then the whole 1.9 cycle seems to be about maximizing pain for all concerned.) -- 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: Missing the Rails 2.3.5 gem.
This problem is detailed here: http://blog.heroku.com/archives/2010/5/25/rails_2_3_6_dependency_issues/ Oren On Wed, Jun 2, 2010 at 3:04 PM, giorgio george.pever...@gmail.com wrote: I get the same message but I dont understand your solution! I have in my Gemfile: gem rails, = 2.3.5, :require = rails But I still get the message Missing the Rails 2.3.5 gem. Please `gem install -v=2.3.5 rails . Just to make it more confusing the app is a clone of another one which works fine on Heroku... Am I missing something? Do I just need to scrap the Heroku app and start again? Cheers George -- 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: Reduce heroku compiled slug size
Don't worry about it. Bamboo has larger slug size due to incorporating everything into your slug. Slug size is the sum of all your gems that's installed plus your application. If you're under 100MB, you're fine. Oren On Wed, May 26, 2010 at 2:23 AM, Estanislau Trepat etre...@gmail.comwrote: I've just updated rails to v2.3.6 on my app under a bamboo-ree-1.8.7 stack and the compiled slug size has grown up to 40.5Mb! Previous to that last git push, the slug size was about 20Mb and was using rails v2.3.5. Is it because my slug has both of rails versions installed? Probably I'm missing something but I haven't added any special code/files into my app as to increase the slug size by ~20Mb. Can you point me on how can I reduce the slug size? Any help will be greatly appreciated. Thank you very much in advance. -- 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: Varnish cache purging
That's wrong. I'll fix the docs. The only way to flush varnish right now is to do a fresh git push. Oren On Sat, May 22, 2010 at 5:05 AM, Daniele to...@vitamino.it wrote: Hi, in the Heroku docs (http://docs.heroku.com/http-caching) I read: Pressing shift-reload in the browser will cue the browser AND (my capitalization) Varnish to regenerate the page, regardless of the cache state. Instead in my experience Varnish does not regenerate the page. Is a bug? Any experience about that? Regards, Daniele -- 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. -- 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: Monitoring Memcached
At this point you can't. Northscale is working on expanding their add-on to offer this type of functionality. Oren On Tue, May 11, 2010 at 2:21 AM, Neil neil.middle...@gmail.com wrote: I'm just wondering how you would go about monitoring your memcache usage/stats for a given application. Any ideas? -- 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. -- 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: Monitoring Memcached
Just heard back from Northscale. The stats command does work.
---
The stats command works and gives per-bucket stats right now,
provided the memcached connection is authenticated, so users should be
able to get their own real-time stats already if they know how to use
it. There are some limitations in libmemcached (used by fauna) as to
how it collects stats, so they won't see every stat we put in there,
but I suspect the stats they can see should be enough for most people.
Here is an example session:
$ irb
require 'Memcached'
= true
mc = Memcached.new('mc2.ec2.northscale.net:11211', :credentials = ['yours',
'***'])
= #Memcached:0x101873a50
@struct=#Rlibmemcached::MemcachedSt:0x101873a00,
@not_found=#Memcached::NotFound: Memcached::NotFound,
@default_ttl=604800, @servers=[mc2.ec2.northscale.net:11211:8],
@options={:poll_timeout=0.25, :hash_with_prefix_key=true,
:default_weight=8, :connect_timeout=4, :ketama_weighted=true,
:logger=nil, :retry_timeout=30, :auto_eject_hosts=true,
:verify_key=true, :support_cas=false, :buffer_requests=false,
:show_backtraces=false, :rcv_timeout=0.25, :use_udp=false,
:hash=:fnv1_32, :sort_hosts=false, :credentials=[yours,
***], :tcp_nodelay=false, :prefix_delimiter=,
:server_failure_limit=2, :binary_protocol=true,
:distribution=:consistent_ketama, :no_block=false,
:cache_lookups=true, :timeout=0.25, :default_ttl=604800},
@not_stored=#Memcached::NotStored: Memcached::NotStored
mc.stats()
= {:bytes_written=[0], :curr_items=[0], :rusage_system=[311.73],
:threads=[4], :limit_maxbytes=[67108864], :cmd_get=[0],
:pointer_size=[64], :total_connections=[45892], :cmd_set=[0],
:bytes=[0], :total_items=[0], :evictions=[0], :time=[1273713737],
:connection_structures=[231], :version=[1.4.4_188_g0117a2c],
:uptime=[262848], :get_hits=[0], :pid=[21691], :bytes_read=[0],
:curr_connections=[202], :rusage_user=[284.26], :get_misses=[0]}
limit_maxbytes is meaningless with our bucket engine, but cmd_* and
*_hits and total_items and bytes are all meaningful on a per-bucket
basis. The main stat you can't see with fauna is engine_maxbytes,
which shows the actual maximum size of the bucket.
Oren
On Wed, May 12, 2010 at 6:05 PM, Jonathan Dance j...@norbauer.com wrote:
I haven't used memcached on Heroku (or in a while), but vanilla
memcached has a stats query you can run, and I think most memcache
clients support this. Not sure if it would provide what you're looking
for, and obviously any monitoring you do you would have to do
yourself. There's some docs for it in the protocol.txt docs for
memcache:
http://code.sixapart.com/svn/memcached/trunk/server/doc/protocol.txt
--wuputah
--
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.
--
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.
Familiar with Azure and willing to talk to the press?
I have a reporter asking us for a user of Heroku who has also used Azure, and can comment on the two. anyone fit that description and willing to talk to the press? 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 at http://groups.google.com/group/heroku?hl=en.
Re: IP Address Range
Unfortunately no. We spin up and down new machines on a daily basis as load changes. Each time we do that, they get a different IP address. Your dynos dynamically move across the machines, so it's impossible to know a source IP address, or even a range beyond the entirety of amazon's address space. I'd check with them if there's any alternative. Oren On Sun, May 2, 2010 at 12:52 PM, Tobes to...@tobinharris.com wrote: We're using SagePay server with our Heroku app (under development right now). SagePay need to know what IP address range the server will post from. Obviously Heroku is on EC2 and uses a range of IPs, can we get the range. In SagePay, we can set up several IP allowed addresses, and can also use C classs subnet masks. Thanks Tobin -- 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: Bug report?: New Relic Bronze Add On having issues on mri-1.9.1 and with Rails 3.0.0.beta2
new relic doesn't support rails 3. On Wed, Apr 28, 2010 at 1:45 AM, Daryl daryl.mann...@gmail.com wrote: Something to check. Adding it in borked my app with no failure messages in heroku logs but removing it brought it back to normal. Have left it out for now. Too bad. It's nice... =] ciao ! Daryl. -- 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: Database timeouts
Sorry guys, it's been a busy few days here. We have been making improvements to our infrastructure to address this. Hopefully no one is seeing any more timeouts after yesterday. If you are, reply back and let us know. Oren On Fri, Apr 23, 2010 at 10:06 AM, djangst djan...@gmail.com wrote: Were you able to get this resolved? I was hoping to see a response from Heroku here--a few database- related questions like yours have gone unanswered in recent months. On Apr 19, 9:17 am, Eric Anderson e...@pixelwareinc.com wrote: I am *hoping* this is just a temp issue with Heroku that will get resolved soon. So in the meantime I created a restart app for my client so they can restart the application themselves if it gets a database hangup. It feels like I am back developing on Windows with having a restart script but it will have to do for now. In case someone else might need something similar here is the code for the restart app: -- 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: What logs get stored by heroku?
we store only ncsa style logs. We don't even store your output from heroku logs - hence only 100 lines. Oren On Mon, Apr 19, 2010 at 1:20 AM, Alex a...@heaton.me wrote: I've got a little sinatra password generating application that I'm confident is secure, but I wanted to make sure no compromising info is being stored in heroku (also, I'm curious). Obviously there are the main logs that sinatra or rails or other frameworks set up, but is there *anything* else that heroku stores behind the scenes about my requests and processes? Looking at my 'heroku logs' output, I'm good, but I wanted to make 100% sure that there isn't anything else being stored anywhere. Thanks, Alex -- 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: Default index page on Heroku server
Did you remove public/index.html?
Oren
On Mon, Apr 19, 2010 at 4:15 PM, Brett brett.huneyc...@gmail.com wrote:
Hi all,
I'm having a problem with the default index page on an app I've
recently uploaded to http://lebronandkobe2.heroku.com.
I want my custom signatures controller to appear instead of the the
standard Rails welcome screen. I changed config/routes.rb
(map.root :controller = signatures), which works on my local
Mongrel server. However it does not work on Heroku. I also ran
heroku rake routes which reports that my change should have worked.
From the log file:
root/
{:action=index, :controller=signatures}
Any advice is much appreciated!
(FYI, the page I am trying to load by default is available
http://lebronandkobe2.heroku.com/signatures)
Thanks!
Brett
--
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: Slug size and websolr-sunspot_rails
your slug limit is 100mb. If you see somewhere saying 20mb, that's a bug. Can you let me know where you saw it so we can update it? Oren 2010/4/12 Tomaž Žlender tomaz.zlen...@gmail.com Hello, slug size of my git repo jumped from 1.9 MB to 21 MB when I added -- version 1.0.3.2 --source http://gemcutter.org' to .gems. Is this normal? My limit for slug is 20mb. Is there anyway to reduce size? Thank you so much for you help. Cheers, Tomaz -- 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: RMagick on bamboo-ree-1.8.7
I don't think bundler uses version. Simply say gem rmagick, 2.12.2 Oren On Sun, Apr 11, 2010 at 4:38 AM, railsnerd rails.n...@gmail.com wrote: Hi there RMagick does not seem to be installed on bamboo-ree-1.8.7 If I do require 'RMagick' at the console it is not found. Are there plans to install it? I tried including it in my Gemfile but it gives the error Can't install RMagick 2.13.1. You must have ImageMagick 6.4.9 or later. Someone on IRC kindly suggested I install an RMagick 2.12.0 which is compatable with ImageMagick 6.3.7, which is on bamboo-ree-1.8.7 However putting this in my Gemfile... gem rmagick, :version=2.12.0, :require=RMagick ... does not work since the version parameter doesn't seem to get picked up? Has anyone got this to work? Or are there any plans to put RMagick on bamboo-ree-1.8.7 thanks :) -- 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.
Looking for a Northscale memcache reference
Hi there, We're getting ready to announce the relationship with northscale. As part of the press activity, we'd like to get a quote from an app using the service. If you're using northscale in a decent way (no hello world apps), and can provide a quote, please contact me directly. Thanks, 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 at http://groups.google.com/group/heroku?hl=en.
Re: sass_on_heroku / hassle
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.
Re: sass_on_heroku / hassle
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: bundler requires RubyGems version = 1.3.6 Errors while deploying a rails 3 app
are you running on the bamboo stack? run heroku stack to see which stack it's set to. Oren On Thu, Mar 25, 2010 at 11:33 AM, Nathan Clark nathanclar...@gmail.comwrote: Hi, I was trying to deploy a sample rails 3 app. I follow the rails 3 document. I followed this as well http://docs.heroku.com/bundler. I have my Gemfile in the root of the sample app. I am getting these errors. - Heroku receiving push - Gemfile detected, running Bundler Unresolved dependencies detected; Installing... Fetching source index from http://gemcutter.org/ Resolving dependencies Installing abstract (1.0.0) from system gems Installing actionmailer (3.0.0.beta) from rubygems repository at http://gemcutter.org/ Installing actionpack (3.0.0.beta) from rubygems repository at http://gemcutter.org/ Installing activemodel (3.0.0.beta) from rubygems repository at http://gemcutter.org/ Installing activerecord (3.0.0.beta) from rubygems repository at http://gemcutter.org/ Installing activeresource (3.0.0.beta) from rubygems repository at http://gemcutter.org/ Installing activesupport (3.0.0.beta) from rubygems repository at http://gemcutter.org/ Installing arel (0.2.1) from rubygems repository at http://gemcutter.org/ Installing builder (2.1.2) from system gems Installing bundler (0.9.13) from rubygems repository at http://gemcutter.org/ /usr/local/lib/ruby/site_ruby/1.8/rubygems/ installer.rb:192:in `install': bundler requires RubyGems version = 1.3.6 (Gem::InstallError) from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/source.rb:42:in `install' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/installer.rb:30:in `run' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/installer.rb:18:in `each' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/installer.rb:18:in `run' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/installer.rb:6:in `install' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/cli.rb:60:in `install' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/vendor/thor/task.rb:33:in `send' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/vendor/thor/task.rb:33:in `run' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/vendor/thor/invocation.rb:109:in `invoke' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/vendor/thor/invocation.rb:116:in `call' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/vendor/thor/invocation.rb:116:in `invoke' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/vendor/thor.rb:137:in `start' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/vendor/thor/base.rb:378:in `start' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/lib/ bundler/vendor/thor.rb:124:in `start' from /usr/local/lib/ruby/gems/1.8/gems/bundler-0.9.9/bin/ bundle:11 from /usr/local/bin/bundle:19:in `load' from /usr/local/bin/bundle:19 FAILED: Have you updated to use a 0.9 Gemfile? http://docs.heroku.com/gems#gem-bundler Any suggestions? -- 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: Excluding development dependencies with Bundler
From talks with the bundler team, they won't be ditching this anytime soon. Ben, How big is your slug? If it's 30 or 40MB, I wouldn't worry about it. Oren On Thu, Mar 25, 2010 at 1:13 PM, Pedro Belo pe...@heroku.com wrote: Hi Ben, Last time I checked Bundler would always download gems, even if you set your environment --without certain groups. They don't show up at the bundler environment file, but they're downloaded in the process of figuring out dependencies. We should check whether it can be patched to not download the full gem. On Wed, Mar 24, 2010 at 6:09 AM, Ben Lavender blaven...@gmail.com wrote: Hello, I'm working on a Rails 3 app using Bundler to specify gems. Like many projects, we have some development-only dependencies, including Webrat. We've got these gems specified in a :test group. On a local machine, we can bring in dependencies without the test dependencies with 'bundle install --without=test'. Is there a way to specify this flag to a heroku deployment? I do not see it in the existing documentation, and Webrat pushes our slug sizes up to 'ridiculous'. Thanks, Ben -- 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.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.
Looking for big data sets - improving data handling
Hi all, we're in the process of improving our data handling, extending taps to make sure it supports bigger data sets of 10GB or larger. To make sure we're covering the right situations, I'm looking for people who have big databases that they can share with us to test with. We'll destroy the data once we're done, we just want to make sure we cover the situation you are using! Let me know if you've got a dataset we can test against. 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 at http://groups.google.com/group/heroku?hl=en.
Re: Heroku technical questions
at this time. [/QUOTE] However, my app would still not start at Mar 14, 2010 - 4:25 UTC. That sounds odd for sure. In the future, make sure to submit a ticket if you're seeing errors. We had no other reports that I'm aware of. It's possible you got unlucky somehow. So, what exactly is the definition of New and idled apps. My understanding is that as long as I'm paying for dynos that my app will not go idle, but if I increase the dynos from say 4 to 10 are the 6 new dynos considered 'new' and won't start in such a situation? What about workers? What about accidentally pushing a 'new' version of code during such an outage? I assume this would effectively bring my running app offline. When issues like this occur, the system automatically identifies it, and prevents users from hurting things. You can't push, you can't change your dynos or workers. We make sure your app continues to run while we find and resolve the issue. 4) If I have a running app that is being concurrently hit by say 100 users. What is the exact process the server takes when I push a new version of code? In other words, do those 100 users immediately get disconnected, or does Heroku spin up the new app, redirecting all new requests to the new version once it is online, and then terminate the 'old' version dynos after all existing requests to those dynos have been satisfied? Basically, what is the user experience for someone who is in the middle of submitting their credit card info at the precise time that I push a new version of code? The latter. Open request are served on the old dynos, which are then replaced with new ones. Users don't see anything. 5) I'm a little concerned about recent posts dealing with getting large datasets in and out of the database on Heroku. I've read plenty of creative ideas on how to get the data in and out, but nothing that would really be considered acceptable for a high traffic site that needs virtually zero downtime (especially with the posts saying that Taps gets really slow after about 500 MB). Does Heroku have any plans of making it easier to get large datasets in and out of the database? What about scaling the database? It's easy to spin up app dynos, but what about moving from a Fugu database to a Zilla? What kind of downtime are we looking at for such a transition? (How about from Ronin - Fugu?) The faqs state: Switching to/from a dedicated database usually takes one business day as our support staff processes the requests, and verifies that data migrations completed successfully. I assume this is for switching between say Koi and Ronin, but is it also true for Ronin-Fugu-Zilla? There's two issues: one the ingress/outgress of big data. We're working on improvements and docs for this. Two - dedicated DB migrations. We handle this for you, and will coordinate with you. It takes 1-2 days to do, with a few minutes of down time each time you switch. That's between any dedicated option. We'll work with you directly to coordinate. 6) I assume I would be looking to move away from Heroku long before I reached 2TB of data limit on the database (since at that point I would be looking for redundant systems that can have read/write traffic separated, etc which Heroku doesn't appear to support), but how would I get this data off Heroku? We haven't had anyone leave due to traffic or size yet. If you start hitting performance bottlenecks, we'd love to work with you to optimize the system or make any changes needed. That said, you can always request a data dump for us if the tools aren't working for you. 7) What systems are used to store the database data? In other words, how safe is my data in the event of system failure (hard disk, etc)? Single disk, Raid 1, Raid 5, Raid 10, etc? Very safe. There's a combination of protection at every layer. SW raid across EBS (which are themselves RAIDed), daily backups of all data, etc. 8) In the event of system failure, what kind of support can I expect from Heroku to get the database back online? (Meaning that a hard disk failure with a response of restore from your backup bundle would not be considered acceptable. Transaction logs would need to be replayed, etc.) We provide full support for this. We'll take care of it for you. 9) DNS related: Is it possible to have say 2 set subdomains for a given domain (ex: forums.mydomain.com, chat.mydomain.com) that point to separate apps, and then have a catchall domain point to a 3rd app? Ex: subdomainXYZ.mydomain.com points to a given app for any value of XYZ. The docs seem to indicate that I need to use the heroku console to add any subdomains, so what I'm looking for is how I would add a catchall domain in Heroku. Wildcard domain, or add each domain independently, your choice. Oren -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to
Re: Heroku technical questions
Hrm, I seem to have lost the first few repies. 1) you can see an archive of all issues here: http://status.heroku.com/past 2) Sigh, I had a long long response here. Short version - we've got advanced monitoring. The pagers went off before any user knew about the problem. We were working on it within 5 minutes. Oren On Mon, Mar 15, 2010 at 9:44 AM, Oren Teich o...@heroku.com wrote: at this time. [/QUOTE] However, my app would still not start at Mar 14, 2010 - 4:25 UTC. That sounds odd for sure. In the future, make sure to submit a ticket if you're seeing errors. We had no other reports that I'm aware of. It's possible you got unlucky somehow. So, what exactly is the definition of New and idled apps. My understanding is that as long as I'm paying for dynos that my app will not go idle, but if I increase the dynos from say 4 to 10 are the 6 new dynos considered 'new' and won't start in such a situation? What about workers? What about accidentally pushing a 'new' version of code during such an outage? I assume this would effectively bring my running app offline. When issues like this occur, the system automatically identifies it, and prevents users from hurting things. You can't push, you can't change your dynos or workers. We make sure your app continues to run while we find and resolve the issue. 4) If I have a running app that is being concurrently hit by say 100 users. What is the exact process the server takes when I push a new version of code? In other words, do those 100 users immediately get disconnected, or does Heroku spin up the new app, redirecting all new requests to the new version once it is online, and then terminate the 'old' version dynos after all existing requests to those dynos have been satisfied? Basically, what is the user experience for someone who is in the middle of submitting their credit card info at the precise time that I push a new version of code? The latter. Open request are served on the old dynos, which are then replaced with new ones. Users don't see anything. 5) I'm a little concerned about recent posts dealing with getting large datasets in and out of the database on Heroku. I've read plenty of creative ideas on how to get the data in and out, but nothing that would really be considered acceptable for a high traffic site that needs virtually zero downtime (especially with the posts saying that Taps gets really slow after about 500 MB). Does Heroku have any plans of making it easier to get large datasets in and out of the database? What about scaling the database? It's easy to spin up app dynos, but what about moving from a Fugu database to a Zilla? What kind of downtime are we looking at for such a transition? (How about from Ronin - Fugu?) The faqs state: Switching to/from a dedicated database usually takes one business day as our support staff processes the requests, and verifies that data migrations completed successfully. I assume this is for switching between say Koi and Ronin, but is it also true for Ronin-Fugu-Zilla? There's two issues: one the ingress/outgress of big data. We're working on improvements and docs for this. Two - dedicated DB migrations. We handle this for you, and will coordinate with you. It takes 1-2 days to do, with a few minutes of down time each time you switch. That's between any dedicated option. We'll work with you directly to coordinate. 6) I assume I would be looking to move away from Heroku long before I reached 2TB of data limit on the database (since at that point I would be looking for redundant systems that can have read/write traffic separated, etc which Heroku doesn't appear to support), but how would I get this data off Heroku? We haven't had anyone leave due to traffic or size yet. If you start hitting performance bottlenecks, we'd love to work with you to optimize the system or make any changes needed. That said, you can always request a data dump for us if the tools aren't working for you. 7) What systems are used to store the database data? In other words, how safe is my data in the event of system failure (hard disk, etc)? Single disk, Raid 1, Raid 5, Raid 10, etc? Very safe. There's a combination of protection at every layer. SW raid across EBS (which are themselves RAIDed), daily backups of all data, etc. 8) In the event of system failure, what kind of support can I expect from Heroku to get the database back online? (Meaning that a hard disk failure with a response of restore from your backup bundle would not be considered acceptable. Transaction logs would need to be replayed, etc.) We provide full support for this. We'll take care of it for you. 9) DNS related: Is it possible to have say 2 set subdomains for a given domain (ex: forums.mydomain.com, chat.mydomain.com) that point to separate apps, and then have a catchall domain point to a 3rd app? Ex
Re: Heroku technical questions
Hrm, I seem to have lost the first few repies. 1) you can see an archive of all issues here: http://status.heroku.com/past 2) Sigh, I had a long long response here. Short version - we've got advanced monitoring. The pagers went off before any user knew about the problem. We were working on it within 5 minutes. Oren On Mon, Mar 15, 2010 at 9:44 AM, Oren Teich o...@heroku.com wrote: at this time. [/QUOTE] However, my app would still not start at Mar 14, 2010 - 4:25 UTC. That sounds odd for sure. In the future, make sure to submit a ticket if you're seeing errors. We had no other reports that I'm aware of. It's possible you got unlucky somehow. So, what exactly is the definition of New and idled apps. My understanding is that as long as I'm paying for dynos that my app will not go idle, but if I increase the dynos from say 4 to 10 are the 6 new dynos considered 'new' and won't start in such a situation? What about workers? What about accidentally pushing a 'new' version of code during such an outage? I assume this would effectively bring my running app offline. When issues like this occur, the system automatically identifies it, and prevents users from hurting things. You can't push, you can't change your dynos or workers. We make sure your app continues to run while we find and resolve the issue. 4) If I have a running app that is being concurrently hit by say 100 users. What is the exact process the server takes when I push a new version of code? In other words, do those 100 users immediately get disconnected, or does Heroku spin up the new app, redirecting all new requests to the new version once it is online, and then terminate the 'old' version dynos after all existing requests to those dynos have been satisfied? Basically, what is the user experience for someone who is in the middle of submitting their credit card info at the precise time that I push a new version of code? The latter. Open request are served on the old dynos, which are then replaced with new ones. Users don't see anything. 5) I'm a little concerned about recent posts dealing with getting large datasets in and out of the database on Heroku. I've read plenty of creative ideas on how to get the data in and out, but nothing that would really be considered acceptable for a high traffic site that needs virtually zero downtime (especially with the posts saying that Taps gets really slow after about 500 MB). Does Heroku have any plans of making it easier to get large datasets in and out of the database? What about scaling the database? It's easy to spin up app dynos, but what about moving from a Fugu database to a Zilla? What kind of downtime are we looking at for such a transition? (How about from Ronin - Fugu?) The faqs state: Switching to/from a dedicated database usually takes one business day as our support staff processes the requests, and verifies that data migrations completed successfully. I assume this is for switching between say Koi and Ronin, but is it also true for Ronin-Fugu-Zilla? There's two issues: one the ingress/outgress of big data. We're working on improvements and docs for this. Two - dedicated DB migrations. We handle this for you, and will coordinate with you. It takes 1-2 days to do, with a few minutes of down time each time you switch. That's between any dedicated option. We'll work with you directly to coordinate. 6) I assume I would be looking to move away from Heroku long before I reached 2TB of data limit on the database (since at that point I would be looking for redundant systems that can have read/write traffic separated, etc which Heroku doesn't appear to support), but how would I get this data off Heroku? We haven't had anyone leave due to traffic or size yet. If you start hitting performance bottlenecks, we'd love to work with you to optimize the system or make any changes needed. That said, you can always request a data dump for us if the tools aren't working for you. 7) What systems are used to store the database data? In other words, how safe is my data in the event of system failure (hard disk, etc)? Single disk, Raid 1, Raid 5, Raid 10, etc? Very safe. There's a combination of protection at every layer. SW raid across EBS (which are themselves RAIDed), daily backups of all data, etc. 8) In the event of system failure, what kind of support can I expect from Heroku to get the database back online? (Meaning that a hard disk failure with a response of restore from your backup bundle would not be considered acceptable. Transaction logs would need to be replayed, etc.) We provide full support for this. We'll take care of it for you. 9) DNS related: Is it possible to have say 2 set subdomains for a given domain (ex: forums.mydomain.com, chat.mydomain.com) that point to separate apps, and then have a catchall domain point to a 3rd app? Ex
Memcache is now in public beta
Hi guys, we'll be putting a blog post up March 16th, but wanted to give you a heads up. Memcached is now in public beta. It's free while in beta, during which time we're making sure we've quashed all the bugs and analyzing usage patterns. Full docs on how to use it is here: http://docs.heroku.com/memcache 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 at http://groups.google.com/group/heroku?hl=en.
Re: Memcache is now in public beta
No, that's one of the main goals of the beta period. We'll be looking at usage patterns, and determine what makes the most sense. Always open to feedback. Oren On Fri, Mar 12, 2010 at 2:11 PM, Terence Lee hon...@gmail.com wrote: Oren, Do you know what the expected price/pricing model is for memcached? -Terence On Fri, 2010-03-12 at 13:33 -0800, Oren Teich wrote: Hi guys, we'll be putting a blog post up March 16th, but wanted to give you a heads up. Memcached is now in public beta. It's free while in beta, during which time we're making sure we've quashed all the bugs and analyzing usage patterns. Full docs on how to use it is here: http://docs.heroku.com/memcache 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 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.
Re: Rails gem missing by default in Bamboo REE 1.8.7 stack
there are no gems at all installed on bamboo. The boot process requires the gem. Is there a reason you vendored the gem? Why not just pin the version in your .gems file instead? Oren On Fri, Mar 12, 2010 at 6:42 PM, Arun Thampi arun.tha...@gmail.com wrote: Hi guys - I tried migrating my deployment stack from 1.8.6 to 1.8.7 and while it was installing Rubygems it raised an error stating that the rails gem is missing by default on the Bamboo platform. I don't need the rails gem since I vendor rails as part of my app, so is there a reason why it forces me to install the rails gem? The migration works fine after I add rails to my .gems file. Thanks for the great platform! Cheers, Arun -- It's better to be a pirate than join the Navy - Steve Jobs http://mclov.in | @iamclovin -- 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.
