Re: Dogpile effect with Varnish?
Hi Ben, Thanks a lot for your answers! I'm looking forward to reading you about the other thread. Thanks! Thomas. On Wed, Oct 13, 2010 at 11:40 PM, Ben Scofield b...@heroku.com wrote: Sorry for the delay! I finally talked to our Varnish expert, and he confirmed that: 1) our configuration should not impede Varnish's default behavior (re: the first question in this thread), and 2) your app's resource configuration (# of dynos, etc.) doesn't affect how much traffic Varnish can handle for it. Our best estimate for Varnish's capacity for a single cached URL is on the order of 4000 requests/second, sustained. I haven't dug deeply into your other thread yet, Thomas -- I'll take another look at it when I can. Ben On Oct 12, 11:13 am, Thomas Balthazar gro...@suitmymind.com wrote: Hi Ben, Any update about this? Thanks, Thomas. On Tue, Oct 5, 2010 at 8:33 PM, Thomas Balthazar gro...@suitmymind.com wrote: Hello Ben, I just read you were about to talk to the Varnish specialist at Heroku. I would really appreciate if you took the time to help me to find the answer to those 2 unanswered questions about Varnish and caching : http://groups.google.com/group/heroku/browse_thread/thread/8e39658d53... http://groups.google.com/group/heroku/browse_thread/thread/fd23e886c2... Thanks in advance for your help! Thomas. On Tue, Oct 5, 2010 at 7:52 PM, Ben Scofield b...@heroku.com wrote: Not sure why this didn't come through earlier, but: I tried out a few experiments, and it looks like our setup doesn't interfere with this default behavior. I'm going to talk to someone with more intimate knowledge of our Varnish config to confirm that, but so far it looks promising. Ben On Oct 5, 12:00 pm, Chris Hanks christopher.m.ha...@gmail.com wrote: Is anyone from Heroku around that might know how their setup works? On Oct 2, 8:42 pm, Chris Hanks christopher.m.ha...@gmail.com wrote: I'm wondering about Heroku's use of Varnish. Suppose I have a page that is expensive to produce (lots of database queries) but can be cached in Varnish. Right after Varnish's copy expires, if it's very popular, I might have a dozen people accessing it simultaneously before the newly created version can be stashed in Varnish. So, based on a thread I found (http://www.gossamer-threads.com/lists/ varnish/misc/14750) it looks like Varnish is smart enough by default to only send that expensive request to my backend once, and serve up the response to all the people waiting for it (to prevent a dogpiling effect). But I know that Heroku has its own configuration for Varnish (with lots of servers in a hash ring), and I was wondering whether it's still set up to do this. 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.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: Dogpile effect with Varnish?
Hi Ben, Any update about this? Thanks, Thomas. On Tue, Oct 5, 2010 at 8:33 PM, Thomas Balthazar gro...@suitmymind.com wrote: Hello Ben, I just read you were about to talk to the Varnish specialist at Heroku. I would really appreciate if you took the time to help me to find the answer to those 2 unanswered questions about Varnish and caching : http://groups.google.com/group/heroku/browse_thread/thread/8e39658d53c53b7c http://groups.google.com/group/heroku/browse_thread/thread/fd23e886c24131b3 Thanks in advance for your help! Thomas. On Tue, Oct 5, 2010 at 7:52 PM, Ben Scofield b...@heroku.com wrote: Not sure why this didn't come through earlier, but: I tried out a few experiments, and it looks like our setup doesn't interfere with this default behavior. I'm going to talk to someone with more intimate knowledge of our Varnish config to confirm that, but so far it looks promising. Ben On Oct 5, 12:00 pm, Chris Hanks christopher.m.ha...@gmail.com wrote: Is anyone from Heroku around that might know how their setup works? On Oct 2, 8:42 pm, Chris Hanks christopher.m.ha...@gmail.com wrote: I'm wondering about Heroku's use of Varnish. Suppose I have a page that is expensive to produce (lots of database queries) but can be cached in Varnish. Right after Varnish's copy expires, if it's very popular, I might have a dozen people accessing it simultaneously before the newly created version can be stashed in Varnish. So, based on a thread I found (http://www.gossamer-threads.com/lists/ varnish/misc/14750) it looks like Varnish is smart enough by default to only send that expensive request to my backend once, and serve up the response to all the people waiting for it (to prevent a dogpiling effect). But I know that Heroku has its own configuration for Varnish (with lots of servers in a hash ring), and I was wondering whether it's still set up to do this. 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.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: Dogpile effect with Varnish?
Hello Ben, I just read you were about to talk to the Varnish specialist at Heroku. I would really appreciate if you took the time to help me to find the answer to those 2 unanswered questions about Varnish and caching : http://groups.google.com/group/heroku/browse_thread/thread/8e39658d53c53b7c http://groups.google.com/group/heroku/browse_thread/thread/fd23e886c24131b3 Thanks in advance for your help! Thomas. On Tue, Oct 5, 2010 at 7:52 PM, Ben Scofield b...@heroku.com wrote: Not sure why this didn't come through earlier, but: I tried out a few experiments, and it looks like our setup doesn't interfere with this default behavior. I'm going to talk to someone with more intimate knowledge of our Varnish config to confirm that, but so far it looks promising. Ben On Oct 5, 12:00 pm, Chris Hanks christopher.m.ha...@gmail.com wrote: Is anyone from Heroku around that might know how their setup works? On Oct 2, 8:42 pm, Chris Hanks christopher.m.ha...@gmail.com wrote: I'm wondering about Heroku's use of Varnish. Suppose I have a page that is expensive to produce (lots of database queries) but can be cached in Varnish. Right after Varnish's copy expires, if it's very popular, I might have a dozen people accessing it simultaneously before the newly created version can be stashed in Varnish. So, based on a thread I found (http://www.gossamer-threads.com/lists/ varnish/misc/14750) it looks like Varnish is smart enough by default to only send that expensive request to my backend once, and serve up the response to all the people waiting for it (to prevent a dogpiling effect). But I know that Heroku has its own configuration for Varnish (with lots of servers in a hash ring), and I was wondering whether it's still set up to do this. 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.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.
Varnish hit limit?
Hey, I was wondering how much traffic can ben handled properly by Varnish. Let's say I have a page with a max-age=3600. Let's say this page gets fireballed, slashdotted, …, at the same time, and gets gazillions of requests non-stop, during 1 hour. Is there a limit in the amount of requests Varnish can handle? Is it linked to the number of Dynos we have? I can't find any information about this in the doc. Thanks a lot for your answer, Thomas. -- 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.
multiple apps with same domain name
Hi, I'm hosting a Webapp on Heroku, with the domain name set to *.myapp.com. (the accounts are the subdomains) But I'd also like to host the public Website for the app on Heroku, with the following domains : myapp.com and www.myapp.com, but when I try to do that, I receive the following message : myapp.com conflicts with an existing custom domain. Is it possible to achieve that? Best, Thomas. --~--~-~--~~~---~--~~ 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: multiple apps with same domain name
Hello, Thanks for your answer. But then, www.myapp.com will go to my Webapp, and not to my public website (they are 2 separate Heroku applications). Am I right? Best, Thomas. On Oct 21, 3:13 pm, Chap c...@chap.otherinbox.com wrote: *.myapp.com is a wildcard for anything.myapp.com Sowww.myapp.comis already covered with the wildcard. On Oct 21, 3:44 am, Thomas Balthazar gro...@suitmymind.com wrote: Hi, I'm hosting a Webapp on Heroku, with the domain name set to *.myapp.com. (the accounts are the subdomains) But I'd also like to host the public Website for the app on Heroku, with the following domains : myapp.com andwww.myapp.com, but when I try to do that, I receive the following message : myapp.com conflicts with an existing custom domain. Is it possible to achieve that? Best, Thomas. --~--~-~--~~~---~--~~ 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: Postgres Invalid Byte Sequence
Hey, I had the same problem during a 'heroku db:push' command, and this solved the problem for me : heroku db:push mysql://r...@localhost/my_db_name?encoding=utf8 HTH, Thomas. On Sep 28, 2:54 pm, aurels aurelien.malis...@gmail.com wrote: Hi, I've exactly the same issue. Has someone solved it since ? Thanks, aurélien --~--~-~--~~~---~--~~ 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: Installing Radiant extension
Hello Keenan, Thanks a lot for your answer. Stupid me. The problem was that the extension was installed as a submodule. I thought that I had verified that, but I was wrong. Sorry for this mistake, and thanks for your help. Everything is working fine. Thomas. And I don't see any error locally. Everything works just fine On Sep 25, 3:46 pm, Keenan Brock kee...@thebrocks.net wrote: Hi Thomas, for testing, sometimes I: chmod -R 555 rails_app chmod 755 rails_app/tmp and I run from there That usually allows me to recreate the problem locally and I go from there. Keep the questions coming, --K On Sep 25, 2009, at 6:02 AM, Thomas Balthazar wrote: Hello John, Thanks a lot for your answer. That's exactly what I did, but the extension isn't activated on Heroku... :-/ Any idea? Best, Thomas. On Sep 25, 5:24 am, john johnm...@gmail.com wrote: the update command for most extensions modifies the file system (adds files to public/javascripts and/or public/stylesheets) so i think you're hitting the read-only filesystem restriction. if it's working locally you can commit all of the changes the extension made and then run: git push heroku master heroku db:push which will copy all the new files (the ones from the update command) and copy up your database (from the migrate command). On Sep 23, 3:52 pm, Thomas Balthazar gro...@suitmymind.com wrote: Hello, I've successfully installed Radiant 0.8.1 on Heroku. Now, I'm trying to install an extension (http://github.com/tricycle/ radiant-page-preview-extension) but I cannot manage to do it. It works perfectly locally, just by running 'rake radiant:extensions:page_preview:update', but when I try to run this command on Heroku 'heroku rake radiant:extensions:page_preview:update' I get the following error : -- rake aborted! Don't know how to build task 'radiant:extensions:page_preview:update' -- I've double-checked, and the 'page_preview' is present in my vendor/ extensions folder. Any idea? Thanks, Thomas. --~--~-~--~~~---~--~~ 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: Installing Radiant extension
Hello John, Thanks a lot for your answer. That's exactly what I did, but the extension isn't activated on Heroku... :-/ Any idea? Best, Thomas. On Sep 25, 5:24 am, john johnm...@gmail.com wrote: the update command for most extensions modifies the file system (adds files to public/javascripts and/or public/stylesheets) so i think you're hitting the read-only filesystem restriction. if it's working locally you can commit all of the changes the extension made and then run: git push heroku master heroku db:push which will copy all the new files (the ones from the update command) and copy up your database (from the migrate command). On Sep 23, 3:52 pm, Thomas Balthazar gro...@suitmymind.com wrote: Hello, I've successfully installed Radiant 0.8.1 on Heroku. Now, I'm trying to install an extension (http://github.com/tricycle/ radiant-page-preview-extension) but I cannot manage to do it. It works perfectly locally, just by running 'rake radiant:extensions:page_preview:update', but when I try to run this command on Heroku 'heroku rake radiant:extensions:page_preview:update' I get the following error : -- rake aborted! Don't know how to build task 'radiant:extensions:page_preview:update' -- I've double-checked, and the 'page_preview' is present in my vendor/ extensions folder. Any idea? Thanks, Thomas. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Installing Radiant extension
Hello, I've successfully installed Radiant 0.8.1 on Heroku. Now, I'm trying to install an extension (http://github.com/tricycle/ radiant-page-preview-extension) but I cannot manage to do it. It works perfectly locally, just by running 'rake radiant:extensions:page_preview:update', but when I try to run this command on Heroku 'heroku rake radiant:extensions:page_preview:update' I get the following error : -- rake aborted! Don't know how to build task 'radiant:extensions:page_preview:update' -- I've double-checked, and the 'page_preview' is present in my vendor/ extensions folder. Any idea? Thanks, Thomas. --~--~-~--~~~---~--~~ 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: HTTP Caching / Rails / etag / last modifed / varnish
Hello Ryan, Did you find the time to test it? Best, Thomas. On Thu, Aug 27, 2009 at 5:33 PM, Ryan Tomayko r...@heroku.com wrote: On Thu, Aug 27, 2009 at 2:07 AM, Thomas Balthazargro...@suitmymind.com wrote: Hello Ryan, Thanks a lot for your in-depth explanation. If I understand you correctly, if I specify : response.headers['Cache-Control'] = public, must-revalidate or expires_in 0, :public = true then the backend will be asked if the content is still fresh for every request, but the backend will only generate a new response if the etag has changed (if the etag hasn't changed, a 304 not-modified header will be sent and the content will be served from the cache, as in the last drawing in your article : http://tomayko.com/writings/things-caches-do ) I tried both solutions, and here are my results : * expires_in 0 : - with Safari, the page doesn't seem to be served from the cache - with Firefox, the page is served from the cache and correctly expired when I create a new item, it is working as expected * response.headers['Cache-Control'] = must-revalidate - with Safari and Firefox : the page is cached but not expired when I create a new item Again, a 15.2Mb screencast that shows it in details : http://dl.getdropbox.com/u/40466/tmp/heroku-caching-2.mov Interesting. I'll dig in and take a look at this today. 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 -~--~~~~--~~--~--~---
Put an application into maintenance state
Hello, I'd like to know what would be the best way to put an application into maintenance state. I want to deploy a major update (code + db structure + data migration) on a Production app, and I'd like to be sure that users don't use the app while I'm deploying and testing. As far as I know, as soon as I run 'git push heroku', the app is deployed and the users are able to access it. The problem is that I haven't run 'heroku rake db:migrate' yet, so the app that is online right now doesn't work. Also, once I've run 'heroku rake db:migrate', I'd like to be able to test the app to be really sure everything is ok. But the users are already using the app and if I made a mistake and I want to rollback, I can't, since users are already using the new DB structure. I know I have to test the app so it doesn't happen, I also have a Staging app to test everything, but, you know, sometimes things still go wrong. So, what would be the best approach to achieve an application 'maintenance' state? Thanks for your suggestions. Best, Thomas. --~--~-~--~~~---~--~~ 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: HTTP Caching / Rails / etag / last modifed / varnish
Hello Ryan, Thanks a lot for your in-depth explanation. If I understand you correctly, if I specify : response.headers['Cache-Control'] = public, must-revalidate or expires_in 0, :public = true then the backend will be asked if the content is still fresh for every request, but the backend will only generate a new response if the etag has changed (if the etag hasn't changed, a 304 not-modified header will be sent and the content will be served from the cache, as in the last drawing in your article : http://tomayko.com/writings/things-caches-do ) I tried both solutions, and here are my results : * expires_in 0 : - with Safari, the page doesn't seem to be served from the cache - with Firefox, the page is served from the cache and correctly expired when I create a new item, it is working as expected * response.headers['Cache-Control'] = must-revalidate - with Safari and Firefox : the page is cached but not expired when I create a new item Again, a 15.2Mb screencast that shows it in details : http://dl.getdropbox.com/u/40466/tmp/heroku-caching-2.mov Do you have any idea? Thanks again for your help, Thomas. On Wed, Aug 26, 2009 at 11:00 PM, Ryan Tomaykor...@heroku.com wrote: On Fri, Aug 21, 2009 at 10:02 AM, Thomas Balthazargro...@suitmymind.com wrote: Hello, I'm trying to use HTTP caching in my Rails 2.3.3 app, but the result is that my pages are always served from the cache even if there is a newer content. I've created a simple Rails app with only one controller to illustrate my problem : 1/ Go here, and you'll see a list of 'items' : http://test-caching.heroku.com/ 2/ Create a new item : http://test-caching.heroku.com/items/new 3/ Go back to the list and you won't see the newly created item because the page is served from the cache : http://test-caching.heroku.com/ Here is a small screencast (8.8Mb) that shows the problem : http://dl.getdropbox.com/u/40466/tmp/heroku-caching.mov Here is the code of the app hosted on Github : http://github.com/suitmymind/heroku-caching/tree/master And the 'caching' code can be found here (lines 8 and 10) : http://github.com/suitmymind/heroku-caching/blob/c7a76c40feda96b357f1d3ef4b09e4f7586add3a/app/controllers/items_controller.rb#L8 Any idea? What am I doing wrong? Thanks a lot for your suggestions. Hi Thomas, Thanks for the detailed example. It looks like Varnish is assuming a default max-age of ~500 seconds since the Cache-Control header is set to public but no explicit max-age is specified and the must-revalidate directive isn't provided. redbot.org is an invaluable resource in debugging these types of issues: http://redbot.org/?uri=http%3A%2F%2Ftest-caching.heroku.com%2F Most HTTP caches support heuristic expiration (details here: http://tools.ietf.org/html/rfc2616#page-80). The basic idea is that, if no explicit expiration time/age is provided, the cache uses a heuristic to determine expiration, typically based on the Last-Modified header. You have a few options here. If you'd like to force the cache to always validate the response with the backend, you can set the must-revalidate cache-control directive. Somewhere before the call to stale?: response.headers['Cache-Control'] = public, must-revalidate That tells the cache that it's not allowed to serve a stale response and that it must validate its version with the backend. Alternatively, you can set the max-age directive to zero. This has pretty much the same effect but looks a lot nicer because Rails has a controller method for it: expires_in 0, :public = true Give those a shot and let me know what happens. I'm also not sure I like that Varnish does heuristic expiration by default, even though it's to spec. 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 -~--~~~~--~~--~--~---
Re: HTTP Caching / Rails / etag / last modifed / varnish
Hello Brian, No I didn't. Thomas. On Wed, Aug 26, 2009 at 4:46 AM, Brian Hammondor.else.it.gets.the.h...@gmail.com wrote: Hi, did you ever find a solution/workaround for this? On Aug 21, 1:02 pm, Thomas Balthazar gro...@suitmymind.com wrote: Hello, I'm trying to use HTTP caching in my Rails 2.3.3 app, but the result is that my pages are always served from the cache even if there is a newer content. I've created a simple Rails app with only one controller to illustrate my problem : 1/ Go here, and you'll see a list of 'items' :http://test-caching.heroku.com/ 2/ Create a new item :http://test-caching.heroku.com/items/new 3/ Go back to the list and you won't see the newly created item because the page is served from the cache :http://test-caching.heroku.com/ Here is a small screencast (8.8Mb) that shows the problem :http://dl.getdropbox.com/u/40466/tmp/heroku-caching.mov Here is the code of the app hosted on Github :http://github.com/suitmymind/heroku-caching/tree/master And the 'caching' code can be found here (lines 8 and 10) :http://github.com/suitmymind/heroku-caching/blob/c7a76c40feda96b357f1... Any idea? What am I doing wrong? Thanks a lot for your suggestions. Best, Thomas. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
HTTP Caching / Rails / etag / last modifed / varnish
Hello, I'm trying to use HTTP caching in my Rails 2.3.3 app, but the result is that my pages are always served from the cache even if there is a newer content. I've created a simple Rails app with only one controller to illustrate my problem : 1/ Go here, and you'll see a list of 'items' : http://test-caching.heroku.com/ 2/ Create a new item : http://test-caching.heroku.com/items/new 3/ Go back to the list and you won't see the newly created item because the page is served from the cache : http://test-caching.heroku.com/ Here is a small screencast (8.8Mb) that shows the problem : http://dl.getdropbox.com/u/40466/tmp/heroku-caching.mov Here is the code of the app hosted on Github : http://github.com/suitmymind/heroku-caching/tree/master And the 'caching' code can be found here (lines 8 and 10) : http://github.com/suitmymind/heroku-caching/blob/c7a76c40feda96b357f1d3ef4b09e4f7586add3a/app/controllers/items_controller.rb#L8 Any idea? What am I doing wrong? Thanks a lot for your suggestions. Best, Thomas. --~--~-~--~~~---~--~~ 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: Staging Environments
Hello Neil, I wrote a post that explains how I deal with a Staging + Production environment here : http://suitmymind.com/blog/2009/06/02/deploying-multiple-environments-on-heroku-while-still-hosting-code-on-github/ Hope this helps. Best, Thomas. On Jul 30, 11:15 am, Neil neil.middle...@gmail.com wrote: Has anyone played with staging environments (in addition to a production environment) on Heroku. Essentially, what I'm looking to achieve is the ability to test deploy my code to Heroku, before trying it against the production version, essentially to just run a final check that things won't explode before trying it against production. It is just a case of adding an additional remote into my git config? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Support response time
Hello, I submitted a support request 4 days ago, and I still have no answer. What is the expected support response time? My app isn't working correctly because of the bug I reported (issue #212) and I still have no clue if there is a solution. I would understand that the support has a lot of work, but I'd really like to know what kind of support service I can expect. My app is not ready for production yet, but support response time is definitely a decisive argument (particularly on a fully managed hosting) to decide if it will go live on Heroku or not. What is your experience with the support? Best regards, Thomas. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Handle incoming e-mails
Hello, I've seen a lot of posts about handling outgoing e-mails. But what would be the best solution to handle incoming e-mails? Having a server elsewhere (Slicehost, Mosso, ...), configured with Postfix and a Rails app that handle/parse incoming e-mails, then ping the Heroku app with the data? Thanks for sharing your ideas. Best, Thomas. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
