Re: Git commands within app
Indeed heroku console is a nice friend, thanks for the noticing git binaries :) But running on a dyno, app is extracted from its repo (thanks Oren) I'm sometimes using a simple heroku-lovely-git-pure workflow (so no deploy task). I would love add locally a post-commit hook on git which would set an env variable. Once deployed my app would use the one on Heroku. It's like Heroku team is already almost doing this (thanks TJ ; I didn't noticed them) : ENV[COMMIT_HASH] ENV[LAST_COMMIT_BY] Why not another little one, `git describe --tag`, which would be (objectively) useful in many use cases ? Thanks :) Clément On May 10, 5:14 pm, Keenan Brock kee...@thebrocks.net wrote: Hi Clem, heroku cosole is your friend. Locally on some stage servers we use Grit. It ran into trouble running on passenger because git was not in the path. Easy to remedy, but since Grit eats the errors - it was a little tricky to track down. For me at least Heroku has git in /usr/bin (do `ls /usr/bin` or Dir['/usr/bin/*'] But it looks like the .git directory is not present in the app. (I did find .gitignore - which was checked into git) I wonder if simply updating your deploy rake task and setting an environment variable with the sha would work for you? --Keenan --Keenan On Tuesday, May 10, 2011 at 9:43 AM, Amokrane wrote: +1. Need this as well. On 9 mai, 07:25, Clément clmntlx...@gmail.com wrote: Ok! Just saying.. Wouldn't it be great to have ENV[DESCRIBE] as well, refering to `git describe` which would allow us to show the current version / tag of the app, and the number of commit from the last tag? Thanks, Have a nice week! Clem On 7 mai, 12:53, 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 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.
Re: Elevated Error Rates
I agree entirely. The messaging needs to have a very strong correlation to reality. If elevated error rates describes a specific thing, we should know exactly what that is. If it covers a range of issues, then the message is insufficient. And, of course, Eric's point about what elevated could possibly mean is spot on. On Tue, May 10, 2011 at 8:19 AM, Eric Anderson e...@pixelwareinc.comwrote: I have noticed that MANY of the messages on http://status.heroku.com generally take the following pattern: 1. We noticed elevated error rates 2. Our engineers are looking into it 3. The error rates have subsided and engineers are monitoring 4. The errors have subsided The issue on 4/28 is a good example but I have seen this pattern before and I am wondering: 1. Why do they use the term elevated error rates. Does this imply there are occasional errors on the Heroku platform normally and they only really start looking into issues when the number of errors gets too high? It seems to be when things are running normal there should be 0 errors coming from the Heroku platform (obviously customer apps will have errors). Or am I reading too much into their wording? 2. They don't really say they did anything. I would expect something like we found the root cause of reason and have done action to fix the problem. But the wording almost implies all they did was monitor the situation and the errors subsided on their own. 3. They say the errors have subsided. Does that means they are just getting the errors back into their acceptable range. Or that they are no errors at all? Is there still some lingering issues? I just find the wording of these status messages very vague and they don't ever give me any confidence that the root cause has been determined and permanently resolved. Am I just reading too much into these messages? -- 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
Hi Clément, I did notice the environment variable: ENV[LAST_GIT_BY] But nothing is stopping you from populating the sha into a config variable upon deploy. On our staging servers we go so far as to display our git information in a status bar. I remember heroku having something like this once upon a time. But that may have been in the heroku 1.0 timeframe. --Keenan On Wednesday, May 11, 2011 at 7:24 AM, Clément wrote: Indeed heroku console is a nice friend, thanks for the noticing git binaries :) But running on a dyno, app is extracted from its repo (thanks Oren) I'm sometimes using a simple heroku-lovely-git-pure workflow (so no deploy task). I would love add locally a post-commit hook on git which would set an env variable. Once deployed my app would use the one on Heroku. It's like Heroku team is already almost doing this (thanks TJ ; I didn't noticed them) : ENV[COMMIT_HASH] ENV[LAST_COMMIT_BY] Why not another little one, `git describe --tag`, which would be (objectively) useful in many use cases ? Thanks :) Clément On May 10, 5:14 pm, Keenan Brock kee...@thebrocks.net wrote: Hi Clem, heroku cosole is your friend. Locally on some stage servers we use Grit. It ran into trouble running on passenger because git was not in the path. Easy to remedy, but since Grit eats the errors - it was a little tricky to track down. For me at least Heroku has git in /usr/bin (do `ls /usr/bin` or Dir['/usr/bin/*'] But it looks like the .git directory is not present in the app. (I did find .gitignore - which was checked into git) I wonder if simply updating your deploy rake task and setting an environment variable with the sha would work for you? --Keenan --Keenan On Tuesday, May 10, 2011 at 9:43 AM, Amokrane wrote: +1. Need this as well. On 9 mai, 07:25, Clément clmntlx...@gmail.com wrote: Ok! Just saying.. Wouldn't it be great to have ENV[DESCRIBE] as well, refering to `git describe` which would allow us to show the current version / tag of the app, and the number of commit from the last tag? Thanks, Have a nice week! Clem On 7 mai, 12:53, 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 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. attachment: dev_bar.png
Rails 3.1 asset pipeline causing 503?
Hello there, I was curious and tried if I can use the new assets pipeline that comes with Rails 3.1 beta (sprockets). From time to time I am getting a 503 for requests of those merged application.js/.css files, an example from my log: 2011-05-11T12:26:10+00:00 app[web.1]: cache: [GET /assets/ application-140d82c5f1fa592792bc01518bd2906e.js] fresh 2011-05-11T12:26:10+00:00 heroku[router]: GET tweektv.heroku.com/ assets/application-140d82c5f1fa592792bc01518bd2906e.js dyno=web.1 queue=0 wait=0ms service=2ms bytes=8700 2011-05-11T05:26:10-07:00 heroku[nginx]: GET /assets/ application-140d82c5f1fa592792bc01518bd2906e.js HTTP/1.1 | 84.191.168.124 | 1325 | http | 503 I am fully aware that this is beta and I did not necessarily expect it to work just so. I'm wondering if this is something related to the app or if this is on Heroku's side anyway (in other words, should I just wait for Rails 3.1 out of beta or not)... The log message isn't very helpful to me, as is what I get in the response of such 503 request (stripped html): Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details. Last not least I have installed the Exceptional Premium add-on and I'm not getting any error notifications in there. Any insight is very much appreciated... --Klaus -- 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: can my APP execute `heroku domain:add #{variable}` ?
Hi, I had the same case in my heroku app and created gem for it: https://github.com/managr/heroku-domainr Cheers, Marcin -- 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: Elevated Error Rates
+1 On Wed, May 11, 2011 at 4:31 AM, John Norman j...@7fff.com wrote: I agree entirely. The messaging needs to have a very strong correlation to reality. If elevated error rates describes a specific thing, we should know exactly what that is. If it covers a range of issues, then the message is insufficient. And, of course, Eric's point about what elevated could possibly mean is spot on. On Tue, May 10, 2011 at 8:19 AM, Eric Anderson e...@pixelwareinc.comwrote: I have noticed that MANY of the messages on http://status.heroku.com generally take the following pattern: 1. We noticed elevated error rates 2. Our engineers are looking into it 3. The error rates have subsided and engineers are monitoring 4. The errors have subsided The issue on 4/28 is a good example but I have seen this pattern before and I am wondering: 1. Why do they use the term elevated error rates. Does this imply there are occasional errors on the Heroku platform normally and they only really start looking into issues when the number of errors gets too high? It seems to be when things are running normal there should be 0 errors coming from the Heroku platform (obviously customer apps will have errors). Or am I reading too much into their wording? 2. They don't really say they did anything. I would expect something like we found the root cause of reason and have done action to fix the problem. But the wording almost implies all they did was monitor the situation and the errors subsided on their own. 3. They say the errors have subsided. Does that means they are just getting the errors back into their acceptable range. Or that they are no errors at all? Is there still some lingering issues? I just find the wording of these status messages very vague and they don't ever give me any confidence that the root cause has been determined and permanently resolved. Am I just reading too much into these messages? -- 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.
Get last deployed time
I want to show my users that my app is still active by showing the last time an update was deployed. How can I get the last time an update was deployed to Heroku from within my app? -- 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.
Could an admin add a subject prefix to this list, like [heroku]
So we can know what list it is without having to open the email. Cheers. -- 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: Could an admin add a subject prefix to this list, like [heroku]
I second this. On May 11, 2011 10:54 AM, Travis Reeder tree...@gmail.com wrote: So we can know what list it is without having to open the email. Cheers. -- 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: Could an admin add a subject prefix to this list, like [heroku]
There is usually good reason why lists don't prefix. Line noise on the subject line being one of them, also the availability of advanced e-mail clients that can do powerful filtering. For instance, in GMail, which both of you use, I can set a filter to label all my Heroku posts. Hence, subject prefixing becomes redundant, and also very irritating when you are trying to identify old messages visually. regards, Richard On Wed, May 11, 2011 at 11:07 PM, Miles Smith wed...@gmail.com wrote: I second this. On May 11, 2011 10:54 AM, Travis Reeder tree...@gmail.com wrote: So we can know what list it is without having to open the email. Cheers. -- 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. -- http://richardconroy.blogspot.com | http://twitter.com/RichardConroy -- 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: Could an admin add a subject prefix to this list, like [heroku]
Well look who slept at a holiday inn express last night! Thanks for the tip Richard. On May 11, 2011 3:20 PM, Richard Conroy richard.con...@gmail.com wrote: There is usually good reason why lists don't prefix. Line noise on the subject line being one of them, also the availability of advanced e-mail clients that can do powerful filtering. For instance, in GMail, which both of you use, I can set a filter to label all my Heroku posts. Hence, subject prefixing becomes redundant, and also very irritating when you are trying to identify old messages visually. regards, Richard On Wed, May 11, 2011 at 11:07 PM, Miles Smith wed...@gmail.com wrote: I second this. On May 11, 2011 10:54 AM, Travis Reeder tree...@gmail.com wrote: So we can know what list it is without having to open the email. Cheers. -- 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. -- http://richardconroy.blogspot.com | http://twitter.com/RichardConroy -- 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: Could an admin add a subject prefix to this list, like [heroku]
I get the filter thing can work, but how about not making everyone on the list create a filter when one person can do it once for the entire list. I don't think the reasons you present are very compelling reasons to not do it. Subject line noise is most welcome when it tells me what list it's from (like your labels) and how does it prevent you from identifying old messages visually? Not meaning to start a big discussion here, just seems like an odd response to a request for something so common. On Wed, May 11, 2011 at 3:20 PM, Richard Conroy richard.con...@gmail.comwrote: There is usually good reason why lists don't prefix. Line noise on the subject line being one of them, also the availability of advanced e-mail clients that can do powerful filtering. For instance, in GMail, which both of you use, I can set a filter to label all my Heroku posts. Hence, subject prefixing becomes redundant, and also very irritating when you are trying to identify old messages visually. regards, Richard On Wed, May 11, 2011 at 11:07 PM, Miles Smith wed...@gmail.com wrote: I second this. On May 11, 2011 10:54 AM, Travis Reeder tree...@gmail.com wrote: So we can know what list it is without having to open the email. Cheers. -- 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. -- http://richardconroy.blogspot.com | http://twitter.com/RichardConroy -- 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: Could an admin add a subject prefix to this list, like [heroku]
I think what Richard is saying is there is no reason to force a change on every user, when a less intrusive (filters) method exists. On May 11, 2011 3:36 PM, Travis Reeder tree...@gmail.com wrote: I get the filter thing can work, but how about not making everyone on the list create a filter when one person can do it once for the entire list. I don't think the reasons you present are very compelling reasons to not do it. Subject line noise is most welcome when it tells me what list it's from (like your labels) and how does it prevent you from identifying old messages visually? Not meaning to start a big discussion here, just seems like an odd response to a request for something so common. On Wed, May 11, 2011 at 3:20 PM, Richard Conroy richard.con...@gmail.com wrote: There is usually good reason why lists don't prefix. Line noise on the subject line being one of them, also the availability of advanced e-mail clients that can do powerful filtering. For instance, in GMail, which both of you use, I can set a filter to label all my Heroku posts. Hence, subject prefixing becomes redundant, and also very irritating when you are trying to identify old messages visually. regards, Richard On Wed, May 11, 2011 at 11:07 PM, Miles Smith wed...@gmail.com wrote: I second this. On May 11, 2011 10:54 AM, Travis Reeder tree...@gmail.com wrote: So we can know what list it is without having to open the email. Cheers. -- 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. -- http://richardconroy.blogspot.com | http://twitter.com/RichardConroy -- 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.
503 error when decreasing dynos
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_closed_without_response). 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.
