Re: Custom domain and https on free tier application

[Neil Middleton]

Custom domains, yes.  HTTPS for free?  No.

On Thu, May 2, 2019 at 8:41 AM Ludovico Fabbri 
wrote:

> Hello everyone!
>
> Two questions about Heroku platform:
>
>
>1. Is it possible to use a custom domain on a free tier application?
>2. Is it possible to setup https on a free tier application?
>
> I just would like to understand if the free tier is sufficient for these
> requirements or do I need at least the hobby plan.
>
> Thank you for any information!
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Account suspended - why?

[Neil Middleton]

Did you email supp...@heroku.com from your account email address?

On Thu, Apr 11, 2019 at 2:06 PM Olivér Atanaszov 
wrote:

> hello!
>
> today I released an app for the National Poetry Day and I kept scaling up
> my app horizontally to serve the increased load throughout the day.
> after some time, I noticed that my account has been suspended. do you know
> anything about Heroku's policy? obviously, I paid for the service...
>
> I can't reach them on chat or phone and they didn't reply to my emails yet.
>
> thanks,
> Oliver
>
>
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Recover data from deleted app

[Neil Middleton]

You’re out of luck there then.  Recovery can normally be done on recently
deleted non hobby DBs, but it’s not done on Hobbys.

On Wed, 3 Apr 2019 at 22:52, Dérick Hogan Pimenta 
wrote:

> Was a DEV PG on a free account.
>
>
> Em 3 de abr de 2019, à(s) 18:22, Neil Middleton 
> escreveu:
>
> Yeah, what type of PG?  Hobby? Premium?
>
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Recover data from deleted app

[Neil Middleton]

Yeah, what type of PG?  Hobby? Premium?

On Wed, 3 Apr 2019 at 21:51, Dérick Hogan Pimenta 
wrote:

> A PG database. The app was deleted a few hours ago
>
>
> Em 3 de abr de 2019, à(s) 17:37, Neil Middleton 
> escreveu:
>
> What sort of database was it?  How long ago?
>
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Recover data from deleted app

[Neil Middleton]

What sort of database was it?  How long ago?

On Wed, 3 Apr 2019 at 21:23, Dérick Hogan Pimenta 
wrote:

> Good afternoon.
>
> Accidentally, I deleted an app from my account, without considering that
> it would also lose access to the database. Is there any way to get a backup
> of the database for the deleted app. I created another app with the same
> name in the illusion that I would get access to the data again. Can you
> guys help me?
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automated testing in Heroku Pipelines

[Neil Middleton]

I use Heroku CI for this.  It does everything in one go, and iirc only
requires a simple link to the appropriate Github repo to work.

On Mon, Aug 7, 2017 at 8:13 PM, Christopher Reichert 
wrote:

> Hi all, my name is Chris and I'm new to the group. I co-founded an app
> called Assertible (https://assertible.com) with my brother that's used to
> automate testing and monitoring of web apps.
>
> I'm curious what services everyone is using to test their apps?
>
> We are using Heroku Pipelines (Review Apps as well) for several different
> services and have come up with a novel way to automate tests each time an
> app is deployed anywhere in a pipeline (based on GitHub deployments).
>
> For example,
>
>   - GitHub deployment initiated by Heroku deployment
>   - Tests are run automatically using the environment URL
>   - Status is reported back to the GitHub PR
>
> End result is API/web app test statuses reported as GitHub Pull Request
> status checks: https://s3-us-west-2.amazonaws.com/assertible/blog/
> assertible-github-status-check.png
>
> Is anyone else using similar testing techniques? I'd love to learn more
> about what's out there.
>
> Cheers,
> -Christopher
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Account Suspended

[Neil Middleton]

In future, tweeting @heroku won't often get a good response as it's more
marketing driven.  Best way is always email supp...@heroku.com or possibly
email this list (although we don't check it regularly)

On Thu, Jan 12, 2017 at 4:46 PM Pete Doherty <pdoherty...@gmail.com> wrote:

> Thank you for your responses, all.
>
> Heroku was made aware of my issue via this mailing list, has reinstated my
> account and is investigating the matter.
>
> Best,
>
> Pete
>
>
> On Thursday, January 12, 2017 at 11:22:36 AM UTC-5, Neil Middleton wrote:
>
> Please don't.  You'll need to create a new account with your regular email
> and send from that if you can't do it from your plussed address.
>
> On Thu, 12 Jan 2017, 16:21 Jason Fleetwood-Boldt, <te...@datatravels.com>
> wrote:
>
>  How extraordinarily annoying.
>
> I will copy & paste the text of this email into  support request for them.
>
> -Jason
>
> On Jan 12, 2017, at 11:17 AM, Pete Doherty <pdohe...@gmail.com> wrote:
>
> Suddenly, I'm seeing the following message when attempting to log into
> Heroku:
>
> The account "me+h...@protonmail.com" has been suspended. If you believe
> this is an error please email sup...@heroku.com.
>
>
> I emailed sup...@heroku.com from my email account (m...@protonmail.com),
> but, I believe, since that address doesn't contain "+heroku", I received a
> reply saying:
>
>
>
> Sorry, the email address you are using has not been recognized as a Heroku
> account.
>
>
> I've also tried tweeting @heroku, but haven't yet received a response.
>
> I'm supposed to be doing client work but am at a standstill because I'm
> not able to deploy their application. Could anyone recommend a next step?
>
> Thanks,
>
> Pete
>
>
> --
> --
> You received this message because you are subscribed to the Google
> Groups "Heroku" group.
>
> To unsubscribe from this group, send email to
>
> heroku+un...@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 Community" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+un...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
>
> 
>
> Jason Fleetwood-Boldt
> te...@datatravels.com
> http://www.jasonfleetwoodboldt.com/writing
>
> If you'd like to reply by encrypted email you can find my public key on
> jasonfleetwoodboldt.com (more about setting GPG: https://gpgtools.org)
>
> --
> --
> You received this message because you are subscribed to the Google
> Groups "Heroku" group.
>
> To unsubscribe from this group, send email to
>
> heroku+un...@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 Community" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+un...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Account Suspended

[Neil Middleton]

Please don't.  You'll need to create a new account with your regular email
and send from that if you can't do it from your plussed address.

On Thu, 12 Jan 2017, 16:21 Jason Fleetwood-Boldt, 
wrote:

>  How extraordinarily annoying.
>
> I will copy & paste the text of this email into  support request for them.
>
> -Jason
>
>
> On Jan 12, 2017, at 11:17 AM, Pete Doherty  wrote:
>
> Suddenly, I'm seeing the following message when attempting to log into
> Heroku:
>
> The account "me+her...@protonmail.com" has been suspended. If you believe
> this is an error please email supp...@heroku.com.
>
>
> I emailed supp...@heroku.com from my email account (m...@protonmail.com),
> but, I believe, since that address doesn't contain "+heroku", I received a
> reply saying:
>
> Sorry, the email address you are using has not been recognized as a Heroku
> account.
>
>
> I've also tried tweeting @heroku, but haven't yet received a response.
>
> I'm supposed to be doing client work but am at a standstill because I'm
> not able to deploy their application. Could anyone recommend a next step?
>
> Thanks,
>
> Pete
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
> 
>
> Jason Fleetwood-Boldt
> t...@datatravels.com
> http://www.jasonfleetwoodboldt.com/writing
>
> If you'd like to reply by encrypted email you can find my public key on
> jasonfleetwoodboldt.com (more about setting GPG: https://gpgtools.org)
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Overriding the policy.xml file for ImageMagick on HTTPS requests.

[Neil Middleton]

Nothing has changed in the last week that would have affected this.  Are
you sure there's no change in the app itself/

On Sat, Dec 10, 2016 at 9:28 PM Mike Johnson 
wrote:

> I am using ImageMagick to read images from a partner server who just
> changed their hosting from http:// to https:// and now the images will
> not get processed using:
>
> `Magick::Image.read(image_path)` when image_path is an https path.
>
>
> After reading more it seems imagemagick vulnerabilities were discovered
> and Heroku implemented a new policy.xml file at
> /etc/ImageMagick/policy.xml
>
>
>
> I read a few guides and tried to create my own policy.xml file, located
> here: /app/.ImageMagick/policy.xml
>
> 
>
>
>
> When I run convert -list policy I get the following output:
>
>
>
>
>
> *Path: /app/.ImageMagick/policy.xmlPolicy: Coderrights: Read pattern:
> HTTPS*
>
>
> *Path: /etc/ImageMagick/policy.xml*
>
>
> *...[OTHER CODERS I WANT TO LEAVE AS IS]*
>
> *...*
>
> *pattern: HTTPS
> *
>
>
> *Policy: Coderrights: None*
>
> *...*
>
> *[MORE CODERS TO LEAVE AS-IS]*
>
> *...*
>
>
>
> It looks like the /etc/ImageMagick/policy.html is overwriting my app
> specific policy.xml. I just want to enable HTTPS for images (read) only.
> This has been working for years until last week.
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Restrict certain URLs to certain IP addresses or ranges.

[Neil Middleton]

Sorry - but this is incorrect.

Rack-timeout only ensures that requests that are hitting a predefined
service time are killed off rather than being allowed to run on consuming
resources.  At the very minimum Rack Timeout should be installed with a
setting of 30s, the same time that the Heroku router will kill a request
with an H12 error.

If you're wanting any sort of DDoS protection and so on, then Rack::Attack
is the one to go for.

However, like I said earlier - IP based security generally adds no real
world actual security.

On Tue, Dec 6, 2016 at 12:13 PM Jason Fleetwood-Boldt 
wrote:

I recommend this great gem for this task, which also serves a double
> purpose of fending off DDOS attacks (which every app should have installed)
>
> https://github.com/heroku/rack-timeout
>
> Using rack-timeout you can set up pretty much any Rack-level restrictions
> you want, including a restriction for a specific part of the app to be
> available only to a whitelisted set of IPs
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Restrict certain URLs to certain IP addresses or ranges.

[Neil Middleton]

This is something you need to do within your app.  There's nothing that
does this at the platform level.

Saying that though, IP spoofing is dead easy so I would question the merit
of doing this at all.

On Tue, 6 Dec 2016, 10:31 Steve Button,  wrote:

> Hi,
>
> Been trying to google for this for a while, and nothing recent + nothing
> seems to actually answer the question.
>
> We have a /admin area within our site, which we would like to restrict to
> a certain range of IP addresses (or list of IPs).
>
> Can this be achieved easily within Heroku?
>
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: heroku nameserver info

[Neil Middleton]

On Mon, Nov 28, 2016 at 3:14 PM Jason Fleetwood-Boldt 
wrote:

>
> You will note that to achieve this, DNSimple reads Heroku's IP addresses *in
> real time* and updates the DNS record in real time with fixed IP
> addresses.
>

Not entirely true as there's a wedge of caching in there, but close enough.
 https://support.dnsimple.com/articles/alias-record/

Yes, if you don't care about SSL at the root (that is, you're ok with
> people either using only http://example.com or https://www.example.com),
> any DNS provider will in fact work for you.
>
> As others said, I too believe GoDaddy to be an inferior DNS provider.
> Contrary to popular opinion, not all DNS is created equally.
>

I wouldn't even call GoDaddy a DNS provider it's that bad.  Move off them
as soon as possible.

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: heroku nameserver info

[Neil Middleton]

I would strongly suggest moving away from GoDaddy DNS, it causes all sorts
of issues.  DNSimple seems to be the best Heroku friendly DNS provider out
there so if you can use them, then do.  They support Apex aliasing along
with everything else you need to get a decent properly configured setup.

On Mon, Nov 28, 2016 at 1:59 PM Pete Keen  wrote:

> Route53 also provides this. You would use an ALIAS record pointing at the
> SSL endpoint that Heroku hands you, which ultimately is an AWS elastic load
> balanced instance.
>
> On Mon, Nov 28, 2016 at 8:26 AM Jennifer Abella 
> wrote:
>
> Jason --
>
> You are the best!  I really appreciate you taking the time to explain this
> to me, a veritable newbie.
>
> Thanks,
> Jen
>
> On Mon, Nov 28, 2016 at 7:53 AM, Jason Fleetwood-Boldt <
> t...@datatravels.com> wrote:
>
> *Heroku does not provide a DNS service.*
>
> You cannot use a traditional DNS service with Heroku, as you said, because
> of the non-permanent IP addresses.
>
> For you, you have two basic options:
>
> 1. Set up a Forwarding domain on GoDaddy. (In this case you keep GoDaddy
> as your primary name server-- every domain *must* have a Primary domain
> name servers). Here, you will want to leave everything as default on
> GoDaddy and set up a CNAME record from your www subdomain to point to the
> domain Heroku assigns to your app (like xyz.herokuapp.com or
> xyz.herokussl.com).
>
> Important: This will not work on the root domain. (That is, if someone
> types in your domain without the "www"). To achieve this, you will need to
> create a Forwarding setup, which can be done inside of GoDaddy, so that
> someone who types http://example.com will get redirected to
> http://www.example.com
>
> *More important*: This root-domain forwarding *will not work if the user
> types in https* instead of *http* on the root domain. (https://example.com).
> It won't work and you can't get it to work. It will never work. You might
> as well just beat your fists against a wall. It is unsupported by GoDaddy +
> Heroku at this time -- you cannot achieve that do not try and do not ask
> them, they cannot help you. It is *not possible* using only GoDaddy and
> Heroku. (That is, I am speaking specifically about SSL at the root-domain
> -- that is specifically impossible.)
>
> 2. If you really want need SSL at the root domain (which is common, as
> without it your users may https://example.com in their browser and be met
> with a message that your site cannot be found), you need to use a
> specialized DNS provider. The only one I know of that currently offers this
> specialized service is DNSimple. We use them and are very happy with them.
> With DNSimple, you will then set GoDaddy to use DNSimple's name servers,
> and DNSimple will then be your primary domain name server. As well, they
> have a special (and magic) service to support SSL at the root domain (as
> explained is impossible with GoDaddy+Heroku only). This is unique in the
> industry and I know of no other DNS provider who offers this special
> service.
>
> Good luck!
>
> -Jason
>
>
>
>
> On Nov 25, 2016, at 8:27 PM, Jennifer Abella 
> wrote:
>
> Help! I'm so new to developing and deploying an app and somehow deleted my
> nameservers on godaddy.com earlier today and need to undo that.  Where
> can I get the nameserver information for Heroku? GoDaddy says they cannot
> help me without the nameserver info or the IP address, which I've read you
> can't really get with Heroku because everything gets moved around.
>
> Thanks,
> Jen
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
> 
>
> Jason Fleetwood-Boldt
> t...@datatravels.com
> http://www.jasonfleetwoodboldt.com/writing
>
> If you'd like to reply by encrypted email you can find my public key on
> jasonfleetwoodboldt.com (more about setting GPG: https://gpgtools.org)
>
> --
> --
> 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 a topic in the
> Google Groups "Heroku Community" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/heroku/IA1pWeRvWBk/unsubscribe.
> To unsubscribe from this group 

Re: Looking to support

[Neil Middleton]

Have you opened a ticket by going to help.heroku.com or emailing
supp...@heroku.com?

On Mon, Jul 18, 2016 at 5:28 PM Kapil Rana  wrote:

> I am unable to get to customer support through official/ non official
> channels. Our app is down. Have made the payment today but it's still down.
> Not getting any revert. Our app services corporate clients and our services
> to them is disrupted.need support urgently.
>
> Regards
>
> Kapil
>
> Birdvision consulting Pvt Ltd.
>
> --
> --
> 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 Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Strange log sequence on Heroku

[Neil Middleton]

Check out the timestamps.  Logging at Heroku is a vastly distributed
system.  Sometimes log lines do get mixed up.  Ordering by the timestamps
will sort this.

On Tue, Apr 21, 2015 at 3:48 PM, Alan Alfredo Rojas Marroquin 
alanroj...@gmail.com wrote:

 Hi everyone.

 I have a Java Play Framework App deployed on Heroku. In my local app when
 I start app I can see this log

 [info] c.z.a.z.o.MessageSubscriber : - Subcribing logger service to redis
 channel...
 *[info] c.z.a.z.o.MessageSubscriber : - Synchronizing loggers...*
 *[error] c.z.a.z.o.MessageSubscriber : - com.zagile: ERROR*
 *[error] c.z.a.z.o.MessageSubscriber : - Level for com.zagile: ERROR*
 *[error] c.z.a.z.o.MessageSubscriber : - Efective Level for com.zagile:
 ERROR*
 [info] a.e.s.Slf4jLogger : - Slf4jLogger started

 But in Heroku I can see this:

 2015-04-21T14:35:05.633291+00:00 app[web.1]: [info]
 c.z.a.z.o.MessageSubscriber : - Subcribing logger service to redis
 channel...
 *2015-04-21T14:35:05.636483+00:00 app[web.1]: [error]
 c.z.a.z.o.MessageSubscriber : - com.zagile: ERROR*
 *2015-04-21T14:35:05.634623+00:00 app[web.1]: [info]
 c.z.a.z.o.MessageSubscriber : - Synchronizing loggers...*
 *2015-04-21T14:35:05.636708+00:00 app[web.1]: [error]
 c.z.a.z.o.MessageSubscriber : - Level for com.zagile: ERROR*
 *2015-04-21T14:35:05.636795+00:00 app[web.1]: [error]
 c.z.a.z.o.MessageSubscriber : - Efective Level for com.zagile: ERROR*
 2015-04-21T14:35:07.192830+00:00 app[web.1]: [info] a.e.s.Slf4jLogger : -
 Slf4jLogger started

 The sequence logs in bold in my local enviroment is right. All of them are
 in same method. But in heroku is not right. *Synchronizing loggers... *should
 be before of *com.zagile: ERROR*

 Maybe you can help to undertand whay this happend.

 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 Community group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to heroku+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Reaching dynos from outside on assigned PORT

[Neil Middleton]

On Mon, Nov 24, 2014 at 11:39 AM, Raman Garg r.m.g...@gmail.com wrote:

 Hi

 1. Could someone share some ways on how to connect(using ssh/telnet etc)
 to dynos remotely using $PORT.
 I got reference from below link from heroku website.
 *https://devcenter.heroku.com/articles/dynos*
 https://devcenter.heroku.com/articles/dynos
 *Dynos are only reachable from outside Heroku via the routers at their
 assigned $PORT*


SSH/telnet is not available.  You cannot connect to an existing dyno is any
way other than HTTP via $PORT


 2. what are the supported protocols and is $PORT customizable?


HTTP, and no.

N

-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Impossible to create an application to Eclipse

[Neil Middleton]

Hi,

I'm pretty sure the eclipse plugin isn't supported any more.

Neil


On Fri, May 30, 2014 at 11:27 AM, Jonathan Jackson 
jonathan.x.jack...@gmail.com wrote:

 I get the same problem and I believe it is because the Heroku/Eclipse
 plugin is not persisting my Heroku Account Email and Password. Check your
 Preferences | Heroku and see if you have same issue.

 Not sure if this is the plugin or Eclipse.

 Sometimes it seems Eclipse has issues persisting security credentials and
 a fix is to create a new Secure Storage password - but this is not working
 for me on this occasion.
 *Preferences | General | Security | Secure Storage* - Password pane and
 simply clicking Windows Integration and choosing Change Password

 I am using Eclipse Kepler Service Release 2.

 On Sunday, April 13, 2014 2:36:56 PM UTC+1, COPINE Patrick wrote:

 Hi,

 After installing the plugin Heroku created in the Eclipse configuration
 side key, I get the following error An unknown error has occurred.
 Persists If this error, please follow up with Heroku*
 support.java.lang.reflect.InvocationTargetException*. Have you an idea
 of this problem?

 Thank you.

  --
 --
 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 Community group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to heroku+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Transferring cost-less app ownership

[Neil Middleton]

What you're seeing here is the transfer of an app that has add-ons
regardless of cost.  Under the current rules, anything that has addons
requires cc verification, just to check you're a real person etc.

Therefore, the new owner needs to be 'verified' before they can receive the
app.

N


On Fri, Apr 4, 2014 at 3:00 PM, leviatan...@gmail.com wrote:

 Good Morning,

 I was trying to transfer the ownership of my app to other registered
 developer.  When develop accepted the ownership he was asked for credit
 card information, regardless app is cost-less.

 Is there a way not to fill card information and transfer ownership, as
 well?

 Thanks in advance
 Leviathan

 --
 --
 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 Community group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to heroku+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Heroku not finding executables

[Neil Middleton]

Hi,

(I answered the ticket)

The problem here, as I described in the ticket isn’t a lack of Unicorn 
specifically, but I just mentioned that was a better option.  The issue here is 
missing binstubs for `rails` and `sidekiq`:

2013-12-23T16:35:50.012859+00:00 app[worker.1]: bundler: command not found: 
sidekiq
2013-12-23T16:35:50.350495+00:00 app[web.2]: bundler: command not found: rails
The default ruby buildpack will run `bundle install --binstubs 
vendor/bundle/bin` which should install these binstubs (which the buildpack 
then symlinks to /bin in your slug).  However, you don’t appear to be using the 
Heroku Ruby buildpack here so anything goes.  More information in the ticket.



- N

On 23 December 2013 at 16:37:30, Qian Wang (qian.wan...@gmail.com) wrote:

Hi everyone, last night I deployed to Heroku and everything crashed as Heroku 
said it could not find rails or sidekiq when it tried to run my Procfile. I had 
just deployed to staging a few hours earlier and that is still running fine and 
has the exact same code + path configurations.

I emailed support who suggested I not use the rails executable and run Unicorn. 
I understand I should probably do that, but seeing as how it could not find 
sidekiq, I don't think that would solve the issue.

Has anyone had experience with Heroku not being able to find executables?

2013-12-23T16:35:48.544030+00:00 heroku[worker.1]: Starting process with 
command `bundle exec sidekiq -C config/sidekiq.yml`
2013-12-23T16:35:48.640832+00:00 heroku[worker.2]: Starting process with 
command `bundle exec sidekiq -C config/sidekiq.yml`
2013-12-23T16:35:49.070889+00:00 heroku[web.2]: Starting process with command 
`bundle exec rails server -p 11442`
2013-12-23T16:35:49.233761+00:00 heroku[worker.2]: State changed from starting 
to up
2013-12-23T16:35:49.236012+00:00 heroku[worker.1]: State changed from starting 
to up
2013-12-23T16:35:49.677581+00:00 heroku[web.1]: Starting process with command 
`bundle exec rails server -p 22096`
2013-12-23T16:35:49.783641+00:00 app[worker.2]: bundler: command not found: 
sidekiq
2013-12-23T16:35:49.783641+00:00 app[worker.2]: Install missing gem executables 
with `bundle install`
2013-12-23T16:35:50.012859+00:00 app[worker.1]: bundler: command not found: 
sidekiq
2013-12-23T16:35:50.012859+00:00 app[worker.1]: Install missing gem executables 
with `bundle install`
2013-12-23T16:35:50.350495+00:00 app[web.2]: bundler: command not found: rails
2013-12-23T16:35:50.350495+00:00 app[web.2]: Install missing gem executables 
with `bundle install`

--
--
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Letting the pager solve R14 Errors

[Neil Middleton]

Yeah, so R14 is more of a warning than an error - your app is still running, 
but much slower than normal.

I would suggest looking at what you’re loading into memory during a worker run 
- I would guess that you’re loading your *entire* app and all it’s dependencies 
in order to do something that I would guess is pretty simple.

- N

On 11 November 2013 at 16:06:32, Jack Royal-Gordon (jac...@pobox.com) wrote:

I have background processes running Sidekiq that run for several hours each 
night. They generate a large number of R14 errors (1600 for 2 processes each 
running about 6-9 hours). But it seems like the excessive memory is slight (not 
more than 520MB vs the 512MB allocated), so it would not be justified to use 
jumbo (1024MB) processes.  

Threads require pre-loading of the runtime environment, which includes the 
Rails library. If there are parts of the library that I'm not using (and there 
are), I ought to be able to fine-tune the pre-load process to exclude them, 
eventually achieving a point where memory usage comes within 512MB. Determining 
which parts are used and which aren't can be a tedious experience. Can I not 
just rely on the paging to eventually page out the parts I'm not using, at 
which point no more paging will take place because the out-of-memory pages are 
never requested?  

I tried lowering the number of concurrent jobs per process (i.e. threads) from 
10 to 8, but it seemed like it only made up 4-5MB in excess memory and did not 
affect the number of R14 errors. In order to make up for the lost concurrency, 
I added another process. The overall effect was to slow everything down (an 
additional 2-1/2 hours of processing to get through the workload), so I 
concluded that the extra concurrency (3x8=24 vs 2x10 = 20) put extra load on 
the Postgre database which became a processing bottleneck. So my gut feeling is 
that changing the jobs-per-process count is not the best way to lower memory 
usage.  

Any other thoughts on how to solve this (or whether it really needs to be 
solved) would be appreciated.  

--  
--  
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 Community group.  
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.  
For more options, visit https://groups.google.com/groups/opt_out.  

-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Issue with root domain

[Neil Middleton]

The problem here is that you're using a now invalid configuration for DNS on 
the Cedar stack.

A few weeks back we changed Cedar so that any 'legacy' DNS configuration to 
proxy.heroku.com would return an H70 error (although this only applies to 
applications created since then).

As always, you should be using the correct the correct DNS configuration as per 
our Custom Domains docs

Neil



On 14 October 2013 at 05:17:32, Prabhu Saitu (prabhu.sa...@gmail.com) wrote:

hey i have a really dumb problem on my hands i have a rails app running on 
cedar stack... ive setup a custom domain the problem is .customdomain.com 
wors but customdomain.com gives an Application Error 

this is the error i get in the logs - Access to bamboo HTTP endpoint denied 
method=GET path=/ host=customdomain.com

i have changed the CNAME record for www.customdomain.com to point to 
myapp.herokuapp.com but the problem still persists

-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Changes in format from heroku logs -p?

[Neil Middleton]

Do you get the same locally when running under Foreman?


On Tue, May 28, 2013 at 1:54 PM, Daniel Doubrovkine dbl...@dblock.orgwrote:

 It looks like the format of `heroku logs -p` has changed.

 ~/source/heroku-commander/dblock$ heroku logs -p run.4296
 2013-05-28T12:48:21.372988+00:00 heroku[run.4296]: Starting process with
 command `(ls -1 21 ; echo rc=$?)`
 2013-05-28T12:48:22.188920+00:00 *app[run.4296]: 
 sequenceId=283416]*Gemfile.lock
 2013-05-28T12:48:22.189065+00:00 app[run.4296]: sequenceId=283426] tmp
 ...
 2013-05-28T12:48:22.188920+00:00 app[run.4296]: sequenceId=283425] script
 2013-05-28T12:48:23.457796+00:00 heroku[run.4296]: Process exited with
 status 0
 2013-05-28T12:48:23.471462+00:00 heroku[run.4296]: State changed from
 starting to complete
 2013-05-28T12:48:31.445353+00:00 heroku[run.4296]: Error R99 (Platform
 error) - Failed to launch the dyno within 10 seconds
 2013-05-28T12:48:31.445517+00:00 heroku[run.4296]: Stopping process with
 SIGKILL

 This looks pretty weird, with an unbalanced ], and is certainly not what's
 documented in https://devcenter.heroku.com/articles/logging#log-format.

 Bug? By design?

 --

 dB. | Moscow - Geneva - Seattle - New York
 code.dblock.org - @dblockdotorg http://twitter.com/#!/dblockdotorg -
 artsy.net - github/dblock https://github.com/dblock

 --
 --
 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 Community group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to heroku+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Changes in format from heroku logs -p?

[Neil Middleton]

Yeah, this looks like a bug in the logplex which will be fixed very soon.
 Sorry if it's caused any problems.

Neil


On Tue, May 28, 2013 at 2:27 PM, John Pignata j...@pignata.com wrote:

 I've just opened a ticket for this same issue. Seems like a bug.

 On Tue, May 28, 2013 at 9:17 AM, dB. dbl...@dblock.org wrote:
  Nope.
 
  ~/source/gravity/dblock$ cat Procfile
  ls: ls -1
 
  ~/source/gravity/dblock$ foreman start ls
  09:16:03 ls.1 | started with pid 70436
  09:16:04 ls.1 | Cheffile
  09:16:04 ls.1 | Cheffile.lock
  09:16:04 ls.1 | Gemfile
  09:16:04 ls.1 | exited with code 0
  09:16:04 ls.1 | Gemfile.lock
  09:16:04 system   | sending SIGTERM to all processes
 
 
 
  On Tuesday, May 28, 2013 9:04:05 AM UTC-4, Neil Middleton wrote:
 
  Do you get the same locally when running under Foreman?
 
 
  On Tue, May 28, 2013 at 1:54 PM, Daniel Doubrovkine dbl...@dblock.org
  wrote:
 
  It looks like the format of `heroku logs -p` has changed.
 
  ~/source/heroku-commander/dblock$ heroku logs -p run.4296
  2013-05-28T12:48:21.372988+00:00 heroku[run.4296]: Starting process
 with
  command `(ls -1 21 ; echo rc=$?)`
  2013-05-28T12:48:22.188920+00:00 app[run.4296]: sequenceId=283416]
  Gemfile.lock
  2013-05-28T12:48:22.189065+00:00 app[run.4296]: sequenceId=283426]
 tmp
  ...
  2013-05-28T12:48:22.188920+00:00 app[run.4296]: sequenceId=283425]
  script
  2013-05-28T12:48:23.457796+00:00 heroku[run.4296]: Process exited with
  status 0
  2013-05-28T12:48:23.471462+00:00 heroku[run.4296]: State changed from
  starting to complete
  2013-05-28T12:48:31.445353+00:00 heroku[run.4296]: Error R99 (Platform
  error) - Failed to launch the dyno within 10 seconds
  2013-05-28T12:48:31.445517+00:00 heroku[run.4296]: Stopping process
 with
  SIGKILL
 
  This looks pretty weird, with an unbalanced ], and is certainly not
  what's documented in
  https://devcenter.heroku.com/articles/logging#log-format.
 
  Bug? By design?
 
  --
 
  dB. | Moscow - Geneva - Seattle - New York
  code.dblock.org - @dblockdotorg - artsy.net - github/dblock
 
  --
  --
  You received this message because you are subscribed to the Google
  Groups Heroku group.
 
  To unsubscribe from this group, send email to
  heroku+un...@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 Community group.
  To unsubscribe from this group and stop receiving emails from it, send
 an
  email to heroku+un...@googlegroups.com.
 
  For more options, visit https://groups.google.com/groups/opt_out.
 
 
 
 
  --
  --
  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 Community group.
  To unsubscribe from this group and stop receiving emails from it, send an
  email to heroku+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/groups/opt_out.
 
 

 --
 --
 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 Community group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to heroku+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Single app with multiple processes vs multiple apps with single process

[Neil Middleton]

Hi,

I'm not entirely sure what issues you're trying to work around here.  Sure,
there's an argument for separation of concerns between
two separate codebases/applications, but aside from that simplicity is a
huge reason for keeping one app as one app.

FWIW, I don't know of anyone using this technique aside
from separating logical parts of an application to scale them separately
 For instance, Heroku split www, dashboard, API and ID up into separate apps

N


On Tue, Apr 16, 2013 at 3:20 PM, Jack R-G jac...@pobox.com wrote:

 Hi Jonas,

 While I agree with all the points JP made, I still chose multiple
 processes in order to achieve greater security.  I maintain information
 provided by my users that is sensitive. I have two apps, one that provides
 all of the front end (web) processing, and a second one that contains all
 the backend (non-web facing) processing.  The only difference between the
 two is configuration: the backend app contains the private keys used to
 secure the data while the frontend app does not.  If a vulnerability exists
 that exposes config (environment) variables to the web, then the private
 key simply would not be available as it does not exist in the front-end
 environment.  I believe that this security enhancement is worth the
 negatives JP mentioned in his response.  I'd like to hear from others if
 they have used this technique, or if they have an informed opinion on
 whether this technique has merit.

 Cheers,

 Jack

 On Monday, April 15, 2013 10:57:52 PM UTC-7, Jonas Windey wrote:

 What are the benefits of putting multiple dyno's (ex. web and worker) on
 a single app compared to putting each dyno on a separate app?
 In terms of scalability, it would be the same since each dyno can be
 scaled no matter how it's setup.

 The only real advantage I could see is that env variables are shared on
 the same app, but that is something that can be overruled in the latter
 setup too.

 The biggest advantage for the second setup is of course a free dyno/month
 for each app.


  --
 --
 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 Community group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to heroku+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: heroku login error

[Neil Middleton]

Can you get to / ping / whatever api.heroku.com?


On Mon, Feb 4, 2013 at 3:19 PM, rxz...@gmail.com wrote:

 Hi Everyone!

 I'm new to heroku. When i execute the command *heroku login** *i get the
 following error. I have cross verified my login credentials multiple times.

 Error Link: http://paste.ubuntu.com/1609191/

 Please help me resolve the prob.

 Thanks in Advance

 --
 --
 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 Community group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to heroku+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: heroku login error

[Neil Middleton]

Sounds to me like you have some sort of connectivity issues to the API
then.  Not sure what I can suggest.


On Mon, Feb 4, 2013 at 3:28 PM, rxz...@gmail.com wrote:

 Hi Neil Middleton,
 I tried the following command
 *ping api.heroku.com
 *PING elb013951-2081682805.us-east-1.elb.amazonaws.com (23.23.122.21)
 56(84) bytes of data


 And it just freezes. Nothing displayed.




 On Monday, February 4, 2013 8:52:32 PM UTC+5:30, Neil Middleton wrote:

 Can you get to / ping / whatever api.heroku.com?


 On Mon, Feb 4, 2013 at 3:19 PM, rxz...@gmail.com wrote:

 Hi Everyone!

 I'm new to heroku. When i execute the command *heroku login** *i get
 the following error. I have cross verified my login credentials multiple
 times.

 Error Link: 
 http://paste.ubuntu.com/**1609191/http://paste.ubuntu.com/1609191/

 Please help me resolve the prob.

 Thanks in Advance

 --
 --
 You received this message because you are subscribed to the Google
 Groups Heroku group.

 To unsubscribe from this group, send email to
 heroku+un...@**googlegroups.com

 For more options, visit this group at
 http://groups.google.com/**group/heroku?hl=en_US?hl=enhttp://groups.google.com/group/heroku?hl=en_US?hl=en

 ---
 You received this message because you are subscribed to the Google
 Groups Heroku Community group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to heroku+un...@**googlegroups.com.

 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




  --
 --
 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 Community group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to heroku+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: heroku push using netrc credentials

[Neil Middleton]

Out of interest, what are you looking to automate?


On Tue, Jan 29, 2013 at 1:55 AM, Matthew Ueckerman duec...@gmail.comwrote:

 As part of automating heroku deployments, I'd ideally like to simplify my
 configuration by having all my heroku crendentials in my .netrc file.
 Consequently I'd like change my remote heroku urls so that they do not
 rely on ssh authentication.

 My current gitconfig looks similar to the following:

 [remote origin]
 fetch = +refs/heads/*:refs/remotes/origin/*
 url = https://github.com/my-repo.git
 [remote heroku]
 fetch = +refs/heads/*:refs/remotes/heroku/*
 url = g...@heroku.com/my-app.git

 Is anyone aware of a http(s) url that can be used to access a remote
 heroku repository?
 Should one be available, is anyone aware of the .netrc entry required for
 this to work - can it be based on the code.heroku.com and 
 api.heroku.comentries?

 Regards,

 Matthew

 --
 --
 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 Community group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to heroku+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
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 Community group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Google API server key IP ranges?

[Neil Middleton]

There's an addon that you can use that gives you a proxy with a fixed IP
but the name escapes me at the moment.  Proxima maybe?

You could add the Amazon ranges but these are changing regularly and still
leave you open to a large chunk of the Internet.

Neil

On Thursday, January 17, 2013, Inactivist wrote:

 Heroku newbie question:

 If I want to deploy an app making use of a Google API's server apps key,
 what IP address ranges should I use when configuring the API keys on
 Google's API Console?  I need to specify a list of acceptable IP ranges,
 which can include a subnet mask like /24 .

 Or, should I use a browser app key?  Will that cause any problems?

 Has anyone done this successfully?  Must I add the entire list of AWS IP
 address ranges https://forums.aws.amazon.com/ann.jspa?annID=1528 ?

 If this has been covered elsewhere, please feel free to drop a link.

 --
 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 javascript:_e({}, 'cvml',
 'heroku%2bunsubscr...@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: app transfer and billing

[Neil Middleton]

No need to email support.  If you transfer ownership, the new owner needs a 
verified CC as the billing just moves over with it.

heroku sharing:transfer b...@example.com 

-- 
Neil


On Wednesday, 9 January 2013 at 14:42, Martin Moss wrote:

 Just email support, and they'll sort it for you
 
 Basically both the owner and the account to be transferred to should email 
 support confirming the transfer, and they'll organise it for you. The billing 
 will transfer to the new owner - or at least this was what happened to us. 
 
 Marty
 
 
 On 17 December 2012 17:46, Josh Coffman joshcoff...@gmail.com 
 (mailto:joshcoff...@gmail.com) wrote:
  Hi,
  
Does anyone know what happens if you transfer an app with paid services 
  to a new owner? We have accounts under 2 different logins, and would like 
  to consolidate to a single account. I'm concerned that paid services will 
  be suspended or lost. 
  
  Thanks,
  josh
  
  -- 
  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 
  (mailto:heroku%2bunsubscr...@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 
 (mailto: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: Ask a web dyno if it is currently up, from the outside?

[Neil Middleton]

Assume that if its taking more than a couple of seconds that this is the
case?

On Wednesday, December 26, 2012, Andrew Lorente wrote:

 Hi,

 I'm writing a commandline client that consumes a web api that currently
 lives in a single web dyno. I'd like the client to be able to tell the user
 hey the dyno is starting up; it'll be a second. Short of having the
 heroku credentials and asking heroku directly, is there any way to get that
 information?

 Andrew

 --
 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 javascript:_e({}, 'cvml',
 'heroku%2bunsubscr...@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: Mixing languages for web worker?

[Neil Middleton]

You probably could create an application running Ruby and JRuby, but you'd be 
looking at making a custom buildpack in order to do this.

An alternative would be to use two apps, and hook them both into the same queue 
- having one app putting items into the queue, and the other just working the 
queue (having no web process).  You can share a database between applications 
easily:  http://neilmiddleton.com/sharing-databases-between-heroku-applications/

You wouldn't even need to modify your code.  Deploy the same app twice, one 
with the Ruby buildpack, and one JRuby, and scale the processes to suit. 

-- 
Neil


On Saturday, 15 December 2012 at 23:39, Brian wrote:

 Hello!
 
 I've got a Rails site up now that let's people create PDF's. The web process 
 does a delayed_job to the worker to create the documents. This is fine, but 
 with the recent announcement of official JRuby support I'd like to look into 
 rewriting my worker in JRuby/iText because it will be much faster than what 
 I'm using for PDF's now (Prawn).
 
 I'm pretty sure I can't but is it possible to mix languages in one app? In my 
 case, I'd like to keep my web process vanilla Ruby, while the worker would be 
 JRuby.
 
 Assuming I can't, what would be the best way to have one Heroku web app queu 
 jobs to another Heroku worker app? 
 
 -- 
 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 
 (mailto: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: [ANN] heroku-forward: beat the 60s application boot timeout

[Neil Middleton]

Interesting.

Does using Heroku pre boot also achieve this or does the 60 second limit still 
apply?  https://devcenter.heroku.com/articles/labs-preboot/
What happens to requests that get routed to the 'live' dyno before the app has 
started?


-- 
Neil


On Thursday, 13 December 2012 at 15:21, Daniel Doubrovkine wrote:

 Many have been struggling with the Heroku R10 boot timeout.
 
 Announcing heroku-forward, a new gem for those with larger or slower 
 applications struggling to boot on Heroku within the 60s timeout limit. See 
 http://artsy.github.com/blog/2012/12/13/beat-heroku-60-seconds-application-boot-timeout-with-a-proxy
  for an introduction.
 
 Of course, it's best not to have this problem and being able to boot your 
 application in less than 60 seconds, but this could be your short/medium term 
 fix when you hit the boot time limit.
 
 Hope it helps,
 
 cheers
 dB.
 
 -- 
 dB. | Moscow - Geneva - Seattle - New York
 dblock.org (http://www.dblock.org) - @dblockdotorg 
 (http://twitter.com/#!/dblockdotorg)
 -- 
 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 
 (mailto: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: [ANN] heroku-forward: beat the 60s application boot timeout

[Neil Middleton]

So there is still the behaviour where your app is effectively down while you're 
waiting for the dynos to spin up?  It looks to me like this gets round the 
issue of preventing deploys from working due to R10 rather than preventing 
H20's?

-- 
Neil


On Thursday, 13 December 2012 at 16:06, Daniel Doubrovkine wrote:

 Heroku-preboot doesn't achieve the same thing: it changes the order in which 
 dynos stop/start - instead of first stopping dynos, then queuing, then 
 starting dynos, it first starts the new dynos, then swaps them after 2 
 minutes. The 60s timeout still applies to the new dynos the same way as it 
 did before.
 
 A request routed to the live dyno is queued inside the dyno (inside the 
 proxy). When all your dynos are queuing, Heroku will queue the request. If a 
 dyno failed to serve the request in 30s, you get an H20 request timeout. To 
 mitigate this, the proxy also supports a delay option that will sleep for 0  
 N  60 seconds waiting for your backend to come up - we run it with 45 
 seconds - our average server boot time is somewhere around 65s and we want to 
 get closer to Heroku's 60s limit (in theory we should set our delay to 59s, 
 but you know, computers aren't that precise :).
 
 On Thu, Dec 13, 2012 at 10:26 AM, Neil Middleton n...@neilmiddleton.com 
 (mailto:n...@neilmiddleton.com) wrote:
  Interesting.
  
  Does using Heroku pre boot also achieve this or does the 60 second limit 
  still apply?  https://devcenter.heroku.com/articles/labs-preboot/ 
  What happens to requests that get routed to the 'live' dyno before the app 
  has started?
  
  
  -- 
  Neil
  
  
  On Thursday, 13 December 2012 at 15:21, Daniel Doubrovkine wrote:
  
  
  
   Many have been struggling with the Heroku R10 boot timeout.
   
   Announcing heroku-forward, a new gem for those with larger or slower 
   applications struggling to boot on Heroku within the 60s timeout limit. 
   See 
   http://artsy.github.com/blog/2012/12/13/beat-heroku-60-seconds-application-boot-timeout-with-a-proxy
for an introduction.
   
   Of course, it's best not to have this problem and being able to boot your 
   application in less than 60 seconds, but this could be your short/medium 
   term fix when you hit the boot time limit.
   
   Hope it helps,
   
   cheers
   dB.
   
   -- 
   dB. | Moscow - Geneva - Seattle - New York
   dblock.org (http://www.dblock.org) - @dblockdotorg 
   (http://twitter.com/#!/dblockdotorg)
   -- 
   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 
   (mailto: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 
  (mailto:heroku%2bunsubscr...@googlegroups.com)
  For more options, visit this group at
  http://groups.google.com/group/heroku?hl=en_US?hl=en
 
 
 
 -- 
 dB. | Moscow - Geneva - Seattle - New York
 dblock.org (http://www.dblock.org) - @dblockdotorg 
 (http://twitter.com/#!/dblockdotorg) 
 -- 
 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 
 (mailto: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: [ANN] heroku-forward: beat the 60s application boot timeout

[Neil Middleton]

Nowhere. Just wondering ;)

On Thursday, December 13, 2012, Daniel Doubrovkine wrote:

 Correct. Where did I say it prevents H20? :)

 On Thu, Dec 13, 2012 at 11:18 AM, Neil Middleton 
 n...@neilmiddleton.comwrote:

 So there is still the behaviour where your app is effectively down while
 you're waiting for the dynos to spin up?  It looks to me like this gets
 round the issue of preventing deploys from working due to R10 rather than
 preventing H20's?

 --
 Neil

 On Thursday, 13 December 2012 at 16:06, Daniel Doubrovkine wrote:

 Heroku-preboot doesn't achieve the same thing: it changes the order in
 which dynos stop/start - instead of first stopping dynos, then queuing,
 then starting dynos, it first starts the new dynos, then swaps them after 2
 minutes. The 60s timeout still applies to the new dynos the same way as it
 did before.

 A request routed to the live dyno is queued inside the dyno (inside the
 proxy). When all your dynos are queuing, Heroku will queue the request. If
 a dyno failed to serve the request in 30s, you get an H20 request timeout.
 To mitigate this, the proxy also supports a delay option that will sleep
 for 0  N  60 seconds waiting for your backend to come up - we run it with
 45 seconds - our average server boot time is somewhere around 65s and we
 want to get closer to Heroku's 60s limit (in theory we should set our delay
 to 59s, but you know, computers aren't that precise :).

 On Thu, Dec 13, 2012 at 10:26 AM, Neil Middleton 
 n...@neilmiddleton.comwrote:

 Interesting.

 Does using Heroku pre boot also achieve this or does the 60 second limit
 still apply?  https://devcenter.heroku.com/articles/labs-preboot/
 What happens to requests that get routed to the 'live' dyno before the app
 has started?

 --
 Neil

 On Thursday, 13 December 2012 at 15:21, Daniel Doubrovkine wrote:

 Many have been struggling with the Heroku R10 boot timeout.

 Announcing heroku-forward, a new gem for those with larger or slower
 applications struggling to boot on Heroku within the 60s timeout limit. See
 http://artsy.github.com/blog/2012/12/13/beat-heroku-60-seconds-application-boot-timeout-with-a-proxyfor
  an introduction.

 Of course, it's best not to have this problem and being able to boot your
 application in less than 60 seconds, but this could be your short/medium
 term fix when you hit the boot time limit.

 Hope it helps,

 cheers
 dB.

 --

 dB. | Moscow - Geneva - Seattle - New York
 dblock.org http://www.dblock.org - 
 @dblockdotorghttp://twitter.com/#!/dblockdotorg

  --
 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: Database migration error

[Neil Middleton]

I've only seen this once before and found that removing the PG add-on and 
re-adding it worked.

-- 
Neil


On Wednesday, 5 December 2012 at 13:50, Harper wrote:

 I'm deploying an app to Heroku for the first time and keep receiving an error 
 when trying to migrate my database. I've looked at all the relevant Heroku 
 docs and asked around at Stack Overflow, but still no luck.
 
 After pushing the code up (which is successful), I run the heroku run rake 
 db:migrate command and see the following:
 
 rake aborted! FATAL: role  is not permitted to log in, followed by 
 the trace which I've posted here. (http://pastebin.com/U5PVUqxc)
 
 According to the guide on postgres errors 
 (https://devcenter.heroku.com/articles/postgres-logs-errors#fatal-role-rolename),
  this error means I don't have a database provisioned. But I know that I do, 
 because running heroku addons | grep POSTGRES returns the database/plan the 
 app is using. I also made sure to store it in the DATABASE_URL config var per 
 Heroku's instructions.
 
 I haven't a clue what is going on, can anyone offer suggestions? Thank you.
 
 
 -- 
 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 
 (mailto: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: How do you track your 503s?

[Neil Middleton]

If you're using an add-on such as Papertrail you can pretty much track what you 
want via your own searches and alerts.  

I'm not sure of any way of doing it with NewRelic.

N 

-- 
Neil


On Monday, 12 November 2012 at 21:53, Jonathan Baudanza wrote:

 I don't know of a way to track 503s, but the Request Queuing measurement in 
 New Relic is helpful. This will tell you if all of your available dynos are 
 being consumed. This may not be related to 503s, but it often is.
 
 On Mon, Nov 12, 2012 at 12:36 PM, Daniel Doubrovkine dbl...@dblock.org 
 (mailto:dbl...@dblock.org) wrote:
  We occasionally get 503s, caused by all kinds of things - a dyno will be 
  sitting in a lock, a database went MIA, Heroku is having trouble, etc. 
  
  How do you track 503s? I'd like to keep their counts, graph, etc. Ideally 
  I'd like to get them in New Relic, but these are errors that happen outside 
  of our dynos. 
  
  Thanks,
  dB.
  
  -- 
  dB. | Moscow - Geneva - Seattle - New York
  dblock.org (http://www.dblock.org) - @dblockdotorg 
  (http://twitter.com/#!/dblockdotorg) 
  -- 
  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 
  (mailto:heroku%2bunsubscr...@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 
 (mailto: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: How do you track your 503s?

[Neil Middleton]

No, AFAIK you can't push stuff into NewRelic (unless their API let's you do 
that).

Essentially Heroku lets you drain your logs into something like Papertrail or 
Loggly.  These logs will include your 503's.
From here you can then setup alerts and suchlike depending on the service 
you're using and do what you will with them.  For instance, you could probably 
push these out to a small app that pushes them onto the NR API (if it let's 
you).

Saying this, this isn't something I've tried - I'm not sure of the benefit of 
getting this data into NR, quite often the logging services will let you 
visualise the data somehow. 

-- 
Neil


On Monday, 12 November 2012 at 22:38, Daniel Doubrovkine wrote:

 Neil, thank you.
 
 Can you elaborate on this? Are you saying I can pull data I have in 
 papertrail right now into New Relic?
 
 On Mon, Nov 12, 2012 at 4:55 PM, Neil Middleton n...@neilmiddleton.com 
 (mailto:n...@neilmiddleton.com) wrote:
  If you're using an add-on such as Papertrail you can pretty much track what 
  you want via your own searches and alerts.  
  
  I'm not sure of any way of doing it with NewRelic. 
  
  N 
  
  -- 
  Neil
  
  
  On Monday, 12 November 2012 at 21:53, Jonathan Baudanza wrote:
  
   I don't know of a way to track 503s, but the Request Queuing 
   measurement in New Relic is helpful. This will tell you if all of your 
   available dynos are being consumed. This may not be related to 503s, but 
   it often is.
   
   On Mon, Nov 12, 2012 at 12:36 PM, Daniel Doubrovkine dbl...@dblock.org 
   (mailto:dbl...@dblock.org) wrote:
We occasionally get 503s, caused by all kinds of things - a dyno will 
be sitting in a lock, a database went MIA, Heroku is having trouble, 
etc. 

How do you track 503s? I'd like to keep their counts, graph, etc. 
Ideally I'd like to get them in New Relic, but these are errors that 
happen outside of our dynos. 

Thanks,
dB.

-- 
dB. | Moscow - Geneva - Seattle - New York
dblock.org (http://www.dblock.org) - @dblockdotorg 
(http://twitter.com/#!/dblockdotorg) 
-- 
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 
(mailto:heroku%2bunsubscr...@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 
   (mailto: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 
  (mailto:heroku%2bunsubscr...@googlegroups.com)
  For more options, visit this group at
  http://groups.google.com/group/heroku?hl=en_US?hl=en
 
 
 
 -- 
 dB. | Moscow - Geneva - Seattle - New York
 dblock.org (http://www.dblock.org) - @dblockdotorg 
 (http://twitter.com/#!/dblockdotorg) 
 -- 
 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 
 (mailto: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 potentially overcharged for scheduler on Oct. 30

[Neil Middleton]

Have you ascertained that your scheduled tasks aren't taking longer than
normal for some reason?  Do you have maximum execution times set in your
code to stop them running indefinitely?

Neil

On Thursday, November 8, 2012, Josh Cronemeyer wrote:

 I've got access to two separate heroku accounts (mine and my employer).
  And several different apps across both accounts that use the basic
 scheduler add on.  I've noticed on my Oct. bill that there is a huge spike
 in usage for all these apps and accounts on Oct. 30.  In all of these
 cases, the amount of processing done by the scheduler is not a function of
 traffic so any spike is unexpected.

 Is anyone else seeing a similar thing on their bill?  I noticed that apps
 that just run a nightly scheduler the net effect is relatively small, but
 if you have scheduler tasks that run every 10 minutes the cost for that
 one anomalous day is pretty big.  My app that schedules every 10 minutes
 went from an average 0.04 dynos to almost 6 dynos on Oct. 30.

 I've filed a support ticket on heroku, but was interested to see if other
 folks were seeing the same issue.

 --
 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 javascript:_e({}, 'cvml',
 'heroku%2bunsubscr...@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: Current Outage and our app

[Neil Middleton]

Indeed - I really doubt this is an all or nothing outage.  Some people will be 
affected - some not.  Out of three of my sites that I just checked, two were 
fine.

FWIW, I wouldn't bother with a support ticket unless status.heroku.com is all 
green and your app is still down.

Neil

On 22 Oct 2012, at 20:13, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote:

 One of my apps (which does not use a database) is up
 
 On Mon, Oct 22, 2012 at 2:05 PM, Joshua McKinney jmckin...@ventanex.com 
 wrote:
 Looks like they are including some apps as well: 
 https://status.heroku.com/incidents/456
 
 
 On Monday, October 22, 2012 1:24:51 PM UTC-5, Joshua McKinney wrote:
 The current outage is only suppose to affect the API but one of our 
 applications is down and we are un-able to open a support ticket...since the 
 api is down.
 
 Anyone else have issue with their application?
 
 Thanks
 
 Josh
 
 -- 
 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

-- 
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: publishing a static website on to Heroku

[Neil Middleton]

Assuming you want to use the Heroku domain for your app.  A custom domain and 
some simple DNS config can go a very long way.

-- 
Neil


On Tuesday, 21 August 2012 at 10:17, Denis Volokhovski wrote:

 Because of different domains. 
 Say, you app got growth and you felt need of server backend in addition to 
 your static site and want to make ajax - 
 it won't be possible due to cross domain request policy s3 - your  server.
 
 Here, you'll be under the same Heroku domain.
 
 The smoothest way for this scenario is proposed by GAE but I do not recommend 
 it anymore.
 
  
 
 
 On Tuesday, March 13, 2012 7:21:59 AM UTC+2, Espen Antonsen wrote:
  Why not just put it on S3?
  
  On Sunday, March 4, 2012 3:03:59 AM UTC+7, Tony Bailey wrote:
   Say, does anyone have a basic tutorial for publishing a static website on 
   to Heroku? I've put up a simple node.js hello world but now have 3-4 
   html files I'd like to package up and put on Heroku.
   
  
  
 
 
 
 -- 
 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 
 (mailto: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: publishing a static website on to Heroku

[Neil Middleton]

It's possible to CNAME an S3 bucket (for instance s3.www.yourdomain.com) and 
have the app on www.yourdomain.com and so on.

Whilst you can't get an exact full domain match you can get pretty close.  It 
depends on the cross domain policies you're using (e.g Flash vs AJAX and so on) 

-- 
Neil


On Tuesday, 21 August 2012 at 10:33, Denis Volokhovski wrote:

 Wait, could you tune custom domain DNS such that the same domain will be 
 linked both to Heroku (server) and to S3 (static site)?
 If it is possible then it is ideal, and very useful information to me!
 
 Denis
 
 
 On Tue, Aug 21, 2012 at 12:26 PM, Neil Middleton n...@neilmiddleton.com 
 (mailto:n...@neilmiddleton.com) wrote:
  Assuming you want to use the Heroku domain for your app.  A custom domain 
  and some simple DNS config can go a very long way.
  
  -- 
  Neil
  
  
  On Tuesday, 21 August 2012 at 10:17, Denis Volokhovski wrote:
  
   Because of different domains. 
   Say, you app got growth and you felt need of server backend in addition 
   to your static site and want to make ajax - 
   it won't be possible due to cross domain request policy s3 - your  
   server.
   
   Here, you'll be under the same Heroku domain.
   
   The smoothest way for this scenario is proposed by GAE but I do not 
   recommend it anymore.
   

   
   
   On Tuesday, March 13, 2012 7:21:59 AM UTC+2, Espen Antonsen wrote:
Why not just put it on S3?

On Sunday, March 4, 2012 3:03:59 AM UTC+7, Tony Bailey wrote:
 Say, does anyone have a basic tutorial for publishing a static 
 website on to Heroku? I've put up a simple node.js hello world but 
 now have 3-4 html files I'd like to package up and put on Heroku.
 
 


   
   
   
   -- 
   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 
   (mailto: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 
  (mailto:heroku%2bunsubscr...@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 
 (mailto: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: New Postgress Plans

[Neil Middleton]

As everything is a VM on EC2, I'm not sure it being a 1 to 1 relationship with 
an EC2 instance makes much difference.

However, saying this, only Crane upwards are described as 'production' 
databases, which brings with it all the things that production stuff brings 
(for instance, priority over the shared stuff). 

-Neil


On Tuesday, 7 August 2012 at 12:03, Neil Middleton wrote:

 As everything is a VM on EC2, I'm not sure it being a 1 to 1 relationship 
 with an EC2 instance makes much difference.  
 
 However, saying this, only Crane upwards are described as 'production' 
 databases, which brings with it all the things that production stuff brings 
 (for instance, priority over the shared stuff). 
 
 -Neil
 
 
 On Tuesday, 7 August 2012 at 11:56, Alex Heaton wrote:
 
  Well Ronin and above match up to various EC2 instances, do multiple 
  Crane/Kappa plans run on 1 instance? 
  
  On Monday, 6 August 2012 23:23:55 UTC+1, Oren Teich wrote:
   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.com 
   (mailto:jeffrey.j.schm...@gmail.com) wrote:
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 
(mailto:heroku%2bunsubscr...@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 
  (mailto: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: Custom domain: Heroku | No such app

[Neil Middleton]

Have you added all the domains to the app itself?

$  heroku domains

N  


On Thursday, 19 July 2012 at 11:25, Łukasz Budnik wrote:

 Hi guys,
  
 I have already used 1 custom domain in Heroku using Zerigo DNS and had no 
 problems at all. But now for last 2 days when I type in my domain  in browser 
 I see Heroku | No such app. I have created a ticket in heroku support system, 
 but I was wondering if there is something else I can do?
  
 I found a StackOverflow post about similar problem in April: 
 http://stackoverflow.com/questions/10298225/heroku-no-such-app. But in April 
 they officially mentioned it on status.heroku.com (http://status.heroku.com), 
 now I don't see anything on status.heroku.com (http://status.heroku.com) and 
 I'm wondering is it only me facing this problem?
  
 Any thoughts?
 Łukasz
  
  
 --  
 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 
 (mailto: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 Rails deploy gem cannot find Heroku credentials

[Neil Middleton]

Can you `heroku login`?

On Thursday, 21 June 2012 at 16:47, planon wrote:

 I am using Heroku Rails gem for deployment..or trying to. I just got this 
 computer and installed my app, and tried to deploy from here, but the gem 
 cannot find my Heroku credentials. 
 
 I'm trying to figure out where they are stored so I can hack it manually. Can 
 anyone tell me where my Heroku credentials are stored? 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 
 (mailto: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: Reverse Proxying

[Neil Middleton]

Is there a valid reason for wanting to avoid serving directly from 
blog.yourapp.com (i.e are 301's sufficient?)

On Wednesday, 20 June 2012 at 16:27, Jeff Schmitz wrote:

 I'd like to set up a reverse proxy, so that requests to myherokuapp.com/blog 
 (http://myherokuapp.com/blog) are served by blog.myherokuapp.com 
 (http://blog.myherokuapp.com) without the user being any the wiser.
 
 However, I haven't seen any way to do this in Heroku.
 
 Has anybody
 
 1) been able to do configure this, or
 2) been able to reverse proxy within their Rails app via gem/plugin, or 
 3) deployed a blog gem/plugin within their Rails app that they love
 
 Tired of losing SEO juice, searching for answers...
 
 Thanks
 
 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 
 (mailto: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: Diagnosing outage

[Neil Middleton]

You'll have trouble diagnosing this outage as the platform was at fault, not 
your application.  The routing layer was having issues for a few minutes 
meaning that HTTP requests would not have been able to reach your application 
(and as this happens in a layer above your application would not show in your 
logs).

Aside from this there are a number of logging options.  The default Heroku 
provided logging add-ons allow you to view up to 24 hours, whereas add-ons such 
as Papertrail allow you to go back pretty much as far as you want (I use 
Papertrail a fair amount on my apps and find it very useful)

More info on Logging / Syslog (how Papertrail works) can be found here:  
https://devcenter.heroku.com/articles/logging

In the meantime, it's a good idea to bookmark the Heroku status site 
(http://status.heroku.com) as, generally speaking, any issues that are outside 
of your control will appear here with more information. 


On Thursday, 7 June 2012 at 23:32, puzzler wrote:

 I've been testing out heroku, with a paid account, to determine
 reliability.
 Got a message from my pingdom account today that my server was down
 for a half-hour.
 
 Looking through the logs for the time in question, I see nothing.
 Specifically, I don't see the router process even reporting that it
 received the pings for the half-hour in question.
 
 One possibly suspicious thing I see is that a half-hour before that, I
 see a web dyno process exiting with code 143 and then restarting, and
 I can't find any documentation about what that means.
 
 Another possibly suspicious thing is that in the two requests
 immediately following the half-hour blank spot in the log, the
 requests show a wait time of about 15ms. The amount seems
 insignificant, but this web server sees so little traffic that the
 wait time is always 0ms. I find it suspicious that the two requests
 immediately following the outage would be the only requests I've ever
 seen to show a wait time.
 
 The main thing I'm realizing is that I really have no idea how to
 troubleshoot outages. The logs that show up when you type heroku
 logs really don't go back that far. Is there a way to get them to go
 back farther? How do I look up what specific exiting codes mean? Any
 idea what could cause web requests to not get through to my app and
 show up in the logs for a half-hour?
 
 Thanks,
 
 mark
 
 -- 
 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 
 (mailto: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: How much dynos has been used so far?

[Neil Middleton]

Indeed - where.  Last time I looked a few weeks back there was a current bill 
amount on the page which you could click for your current invoice - it appears 
that this has now been removed.  Sorry about that.

So, to answer your original question - I don't know ;) 


On Thursday, 7 June 2012 at 08:08, Linus Pettersson wrote:

 Hmmm. Where?
 
 If I go to Account I can see Past Invoices. I got a tip at SO to check 
 out:
 https://api.heroku.com/invoices/current
 
 But, that seems to be the latest invoice only. It currently ranges from May 
 01 - June 01, 2012. What about June 01 - Today. That's what I want to see. I 
 don't like to get the surprise at the end of the month :)
 
 Regards
 Linus
 
 
 Den onsdagen den 6:e juni 2012 kl. 22:26:14 UTC+2 skrev Neil Middleton:
  The invoices are pretty much the most up to date data available - AFAIK 
  they update around once a day.
  
  On Wednesday, 6 June 2012 at 21:24, Linus Pettersson wrote:
  
   Hi!
   
   Is there a way to see how many dyno hours you have used so far this month 
   on Heroku? I know it's on the invoice you get, but I want some live 
   data.
   
   I use some One off processes (heroku run rake...) quite often and want 
   to track this somehow.
   
   Cheers!
   Linus
   
   -- 
   You received this message because you are subscribed to the Google
   Groups Heroku group.

   To unsubscribe from this group, send email to
   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 
 (mailto: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: How much dynos has been used so far?

[Neil Middleton]

The invoices are pretty much the most up to date data available - AFAIK they 
update around once a day.

On Wednesday, 6 June 2012 at 21:24, Linus Pettersson wrote:

 Hi!
 
 Is there a way to see how many dyno hours you have used so far this month on 
 Heroku? I know it's on the invoice you get, but I want some live data.
 
 I use some One off processes (heroku run rake...) quite often and want to 
 track this somehow.
 
 Cheers!
 Linus
 
 -- 
 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 
 (mailto: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: Installing the Heroku Commands

[Neil Middleton]

http://stackoverflow.com/questions/tagged/heroku

Neil


On Tuesday, 22 May 2012 at 20:16, Jeff SKI Kinsey wrote:

 I don't know what post to Stack Overflow means..
 

-- 
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: memory quota exceeded error

[Neil Middleton]

Are you using unicorn by any chance? If so, drop the number of workers you're 
running.  

-Neil


On Wednesday, 23 May 2012 at 21:05, Josh Coffman wrote:

 I'm getting Error R14 fairly regularly on one rails app. Anyone have 
 suggestions on tracking this down and how to handle it? 
 
 Thanks,
 Josh
  
 
 -- 
 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: Scheduler Re-running Tasks?

[Neil Middleton]

 Suggestion for those with email jobs tied to scheduler.  It maybe useful to 
 have some code to check that the email only get sent once.  

To be honest, this should probably be built into any code that causes problems 
if it runs more than once.  For instance, in your case, it's bad if an email is 
sent twice.  It could be a billing job that would cause problems if it charged 
twice etc.

In some ways that should be in the requirements for the code, and thus the 
tests.  For instance, I have invoicing jobs that run every hour, but 99% of the 
time will decide to do nothing, but they run that frequently to ensure the 
timeliness of an invoice when one is required.

N

-- 
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: Will my *.herokuapp.com app get indexed by Google and other search engines?

[Neil Middleton]

Same with any website out there - if there's a link to it that Google can 
discover the site through, and the robots.txt/headers allow, it'll get indexed.

Neil


On Saturday, 28 April 2012 at 01:31, sabhansali wrote:

 Hey, I'm just wondering if my application that is hosted on herokuapp.com 
 (http://herokuapp.com) will get indexed by Google and other search engines.
 Thanks,
 Siddharth
 
 -- 
 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 
 (mailto: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: Imminent Death of the Heroku Google Group

[Neil Middleton]

Our of interest, what do people think is the ideal form of community support 
for something like Heroku?  Lots use SO, and lots hang out here. 

-Neil 

On 27 Apr 2012, at 21:19, Justin Houk jsh...@gmail.com wrote:

 That does seem the option that does the least harm to the existing community. 
  I am among those who appreciate the stream of Heroku-related information 
 this group provides through my inbox, which is a service neither 
 support.heroku.com nor SO provides.  I would be happy if it would remain 
 available as a community group rather than being completely erased when 
 Heroku withdrew active support.
 
 --Justin
 
 On Fri, Apr 27, 2012 at 3:43 PM, Sara Dornsife s...@heroku.com wrote:
 Yes, reconsidering the prior decision. One idea is to keep a Google Group 
 going, same members, but have it be a community group not a branded Heroku 
 group where troubleshooting can still occur.
 Sara
 
 On Apr 26, 2012, at 3:11 PM, Randy Regnier wrote:
 
  I guess I'm more confused now with the the clarification statement. Your 
  first statement laid out a decent business case for closing this list. 
  Reasonable people can agree or disagree with the conclusion, but it was a 
  decent enough option, given the data provided. But, now it appears you 
  would like to have more discussion. Are you reconsidering the prior 
  decision to close the list or just going through some exercise? There isn't 
  much point in trying to argue the case to keep it open, if the conclusion 
  can't be changed.
 
  Randy
 
  On 4/25/2012 2:24 PM, Sara Dornsife wrote:
  Let me apologize again for the miscommunication. I screwed up. Let me also 
  elaborate on my previous response.
 
  As you know (and hopefully one of the reasons you guys love us), we move 
  fast. Sometimes, too fast. This went from an idea to a note in a 
  newsletter very quickly without the appropriate process we should apply to 
  it. I take responsibility for this.
 
  We want to involve you guys. By definition, if you're on this list, you 
  are passionate supportive developers that we love and consider a core part 
  of Heroku. This step was inappropriately skipped.
 
  Here's the baseline we're operating from:
  - Through support, we hear regularly from users who are frustrated with 
  this group and the lack of response they received.
  - Prospects are looking for a thriving community as part of their 
  evaluation of Heroku. I say prospects here meaning individual 
  developers, not just enterprise level customers. This Google Group isn't 
  that. The traffic is low enough that it appears to mean we don't have an 
  active community.
  - Stack Overflow has to grown to actually be a better place for getting 
  answers many times than this Google Group. Traffic there is WAY higher 
  than this group.
  - Heroku would like to officially participate more actively in community 
  work. Spreading our efforts has a cost.
 
  With that baseline, we have discussed internally focusing our users and 
  community efforts on Stack Overflow. That consideration should have been 
  discussed here, soliciting your feedback and suggestions.
 
  While we didn't get the sequence right, we do have the discussion going 
  now. Let's treat it as that - a discussion.
 
  I see a few topics to discuss:
  - Focusing Heroku's community efforts in SO
  - Leaving this group up
  - Shutting this group down
  - Other ideas
 
  Am I missing anything?
  Sara
 
 
  On Apr 25, 2012, at 1:28 PM, Ted Husted wrote:
 
  Hmmm, if any of us here agreed with any of those (unsubstantiated)
  statements, then we wouldn't be here.
 
  -Ted.
 
 
  On Wed, Apr 25, 2012 at 2:22 PM, Sara Dornsifes...@heroku.com  wrote:
  I'm Sara Dornsife, Dir of Dev Mktg at Heroku. Sorry for not introducing
  myself earlier. Also sorry for not posting here about wanting to close 
  this
  list before it hit the newsletter.
 
  List traffic has been low and very often the questions/comments posted 
  here
  are best resolved on support.heroku.com. At the same time, Stackoverflow
  usage has continued to grow and the community there is very active.
 
  For those reasons, we feel its best to consolidate to support and
  Stackoverflow.
  Sara
 
  --
  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
 
 
 
 -- 
 Justin Houk
 Co-Founder, 10x10 Room
 http://www.linkedin.com/profile/view?id=6055184
 http://10x10room.com
 http://playconclave.com
 
 -- 
 You received this message because you are subscribed to the Google
 Groups Heroku 

Re: Imminent Death of the Heroku Google Group

[Neil Middleton]

In order to play devils advocate here (I'm not saying if I'm on one side of the 
fence or the other):

1) The group isn't a great archive for problems as the specific problems tend 
to be buried in email threads.
2) For a lot of the problems on here, support.heroku.com is probably the best 
place to go.
3) The StackOverflow  tag on SO is remarkably active:  
http://stackoverflow.com/questions/tagged/heroku
3) Google have already done this with some success:  
https://groups.google.com/forum/?fromgroups#!topic/google-appengine/Z6XN_64cA7w


Neil


On Wednesday, 25 April 2012 at 18:12, Alex Chaffee wrote:

 fIn the latest Heroku Newsletter[1], it says this group will be killed
 at the end of April, and suggests instead to go to support.heroku.com 
 (http://support.heroku.com)
 (which is private) or stackoverflow.com (http://stackoverflow.com). While SO 
 is awesome, is it
 really an adequate replacement for this group? I've found that SO is a
 great complement to mailing lists but doesn't allow for the same kind
 of deep discussion and community building. Worse, it requires active
 attention rather than arriving in one's inbox, so the people who are
 most likely to have an answer to a question are the least likely to
 hear it -- since they're not having any problems.
 
 Why uproot a productive community (this mailing list) and hope that it
 migrates to a new place with a radically different interaction model?
 
 [1] 
 http://lists.heroku.com/t/ViewEmail/r/6DFC781E555FD71E/CEC5941F8B0A6F4BC5EC08CADFFC107B
 
 -- 
 Alex Chaffee - a...@stinky.com (mailto:a...@stinky.com)
 http://alexchaffee.com
 http://twitter.com/alexch
 
 -- 
 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 
 (mailto: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: git tagging heroku releases

[Neil Middleton]

You've lost me a little here.  `heroku releases` gives you all the deployed git 
versions and other changes.  For instance:

Rel   Change  ByWhen
  --  ----
v214  Deploy 5f3f619  neil.middle...@gmail.com2012-04-18 
17:28:41 +0100
v213  Deploy b71ce95  neil.middle...@gmail.com2012-04-12 
15:04:45 +0100
v212  Deploy d27f151  neil.middle...@gmail.com2012-04-12 
13:20:53 +0100
v211  Deploy 6b81eef  neil.middle...@gmail.com2012-04-12 
12:59:28 +0100
v210  Config add FACEBOOK_APP_SECR..  neil.middle...@gmail.com2012-04-12 
12:56:11 +0100
v209  Deploy 2f54f24  neil.middle...@gmail.com2012-04-12 
11:43:28 +0100
v208  Deploy 19b486d  neil.middle...@gmail.com2012-04-12 
11:36:34 +0100
v207  Deploy efdd6ef  neil.middle...@gmail.com2012-04-12 
11:22:40 +0100

Each of those deploy hashes under 'Change' match commits in my Git repo on 
Github (and everywhere else).

By rolling back to say v208 I know I'm going to end up with 19b486d, or am I 
missing something obvious here?

N


Neil


On Monday, 23 April 2012 at 02:08, david ignacio wrote:

 Hey-
 
 So one thing that has got me about heroku is that there isn't
 necessarily a good link between the git repo and heroku releases. By
 this I mean that it isn't entirely obvious what is deployed and
 running at the moment. There are two current tools we have:
 * the heroku remote in the git repo
 * heroku releases
 
 This gives me the current release and what is working right now, but
 nothing more. If I deploy something broken, there isn't a clear way
 to find what I'd be rolling back to. The hashes displayed in heroku
 releases are of the compiled slugs.
 
 I have gone through a few back and forths as to what would be a good
 way to fill this gap. I realized that you'd really need two different
 scripts since releases are created in multiple places, one in the
 heroku cli and one in git. The config/addon changes trigger a new
 release to be created, but I think that those changes are well
 documented in heroku releases. It was the git-push triggered releases
 that I wanted to track.
 
 This led me to write: https://github.com/deignacio/gthr
 
 What I'm wondering from you guys is:
 * is there any other way in heroku that I can get the information I'm
 scraping so that I'm not just scraping stderr of git push?
 * am I thinking about this problem in the right way that this
 solution seems okay?
 * are there any other precedents that I didn't find in my sanity
 check google search?
 * assuming that the previous questions are positive, can anyone think
 of any other things they'd want?
 
 Thanks for your input
 Dave
 
 -- 
 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 
 (mailto: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: git tagging heroku releases

[Neil Middleton]

Something that tagged your Git repo with release information prior to a deploy 
would definitely be helpful to some people.

Neil


On Monday, 23 April 2012 at 16:07, david ignacio wrote:

 Well that's embarrassing. Looks like when I found the need for this,
 I had several issues in my repo/app running in concert. This made me
 think that when the hashes listed in `heroku releases` differed from
 both `git log heroku/master` and `git log master` that I was perhaps
 seeing an alternate hash generated by the slug compilation.
 
 Don't mind me I guess, at least I only spent a day or so on this
 script, although I think that perhaps then converting the idea into a
 heroku cli plugin that just took the versions in releases and created
 the tags as scraped could still have value?
 
 Thoughts?
 
 On Mon, Apr 23, 2012 at 09:10, Neil Middleton neil.middle...@gmail.com 
 (mailto:neil.middle...@gmail.com) wrote:
  You've lost me a little here.  `heroku releases` gives you all the deployed
  git versions and other changes.  For instance:
  
  Rel   Change  ByWhen
    --  ----
  v214  Deploy 5f3f619  neil.middle...@gmail.com 
  (mailto:neil.middle...@gmail.com)2012-04-18
  17:28:41 +0100
  v213  Deploy b71ce95  neil.middle...@gmail.com 
  (mailto:neil.middle...@gmail.com)2012-04-12
  15:04:45 +0100
  v212  Deploy d27f151  neil.middle...@gmail.com 
  (mailto:neil.middle...@gmail.com)2012-04-12
  13:20:53 +0100
  v211  Deploy 6b81eef  neil.middle...@gmail.com 
  (mailto:neil.middle...@gmail.com)2012-04-12
  12:59:28 +0100
  v210  Config add FACEBOOK_APP_SECR..  neil.middle...@gmail.com 
  (mailto:neil.middle...@gmail.com)2012-04-12
  12:56:11 +0100
  v209  Deploy 2f54f24  neil.middle...@gmail.com 
  (mailto:neil.middle...@gmail.com)2012-04-12
  11:43:28 +0100
  v208  Deploy 19b486d  neil.middle...@gmail.com 
  (mailto:neil.middle...@gmail.com)2012-04-12
  11:36:34 +0100
  v207  Deploy efdd6ef  neil.middle...@gmail.com 
  (mailto:neil.middle...@gmail.com)2012-04-12
  11:22:40 +0100
  
  Each of those deploy hashes under 'Change' match commits in my Git repo on
  Github (and everywhere else).
  
  By rolling back to say v208 I know I'm going to end up with 19b486d, or am I
  missing something obvious here?
  
  N
  
  
  Neil
  
  On Monday, 23 April 2012 at 02:08, david ignacio wrote:
  
  Hey-
  
  So one thing that has got me about heroku is that there isn't
  necessarily a good link between the git repo and heroku releases. By
  this I mean that it isn't entirely obvious what is deployed and
  running at the moment. There are two current tools we have:
  * the heroku remote in the git repo
  * heroku releases
  
  This gives me the current release and what is working right now, but
  nothing more. If I deploy something broken, there isn't a clear way
  to find what I'd be rolling back to. The hashes displayed in heroku
  releases are of the compiled slugs.
  
  I have gone through a few back and forths as to what would be a good
  way to fill this gap. I realized that you'd really need two different
  scripts since releases are created in multiple places, one in the
  heroku cli and one in git. The config/addon changes trigger a new
  release to be created, but I think that those changes are well
  documented in heroku releases. It was the git-push triggered releases
  that I wanted to track.
  
  This led me to write: https://github.com/deignacio/gthr
  
  What I'm wondering from you guys is:
  * is there any other way in heroku that I can get the information I'm
  scraping so that I'm not just scraping stderr of git push?
  * am I thinking about this problem in the right way that this
  solution seems okay?
  * are there any other precedents that I didn't find in my sanity
  check google search?
  * assuming that the previous questions are positive, can anyone think
  of any other things they'd want?
  
  Thanks for your input
  Dave
  
  --
  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 
  (mailto: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 
  (mailto: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

Re: issues with asset sync

[Neil Middleton]

A bit of background as to what is going on here might be helpful.

When you push your code into Heroku a set of machines will take that code
and compile it into a slug.  This slug is what is deployed to the dynos
when required.  Due to a few reasons, these slug compilers are not aware of
the application environment - this only comes into play when the slug meets
the dyno.  So therefore, when asset sync is trying to access your
environment during the build process (which the buildpacks control if
you've seen them) then it doesn't find anything.

Now, there's a couple of options round this.  Firstly, you can run `heroku
run rake assets:precompile` once you're up and deployed.  All rake tasks
have access to your environment so this will run just fine.  Secondly, you
can use the user-env-compile plugin that Daniel mentioned, but be aware
this is beta so could be changed/yanked at any time.  A third option is as
Richard suggests (although only applies if using cloudfront) and let
Cloudfront pull the files from your dynos first time their needed and not
use asset sync at all.  I guess it all depends on what your needs are.

N

On Fri, Apr 20, 2012 at 5:33 PM, brianthecoder wbsmit...@gmail.com wrote:

 So I followed the guide here
 https://devcenter.heroku.com/articles/cdn-asset-host-rails31, but for
 some reason, during the assets:precompile rake task. Its not picking up any
 of my environment variables. I even added a line to inspect the environment
 variables in the asset_sync initalizer, and none of the environment
 variables I have configured were in there. Am I missing something?

 --
 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




-- 
Neil

-- 
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: confused about best practices for CNAME records

[Neil Middleton]

Ideally you want everything to be a CNAME of your Heroku URL (app.herokuapp.com 
etc).  The problem is is that the DNS spec doesn't allow the Apex domain to be 
CNAME'ed.  The solution is to use Zerigo or DNSimple who provide workarounds.

Full writeup here:  
http://neilmiddleton.com/the-dangers-of-a-records-and-heroku/


Neil


On Tuesday, 3 April 2012 at 01:24, Justin Collum wrote:

 Hi, I have an app that's set up at http://gentle-wind-.herokuapp.com/. On 
 my hover.com (http://hover.com) account in the DNS I have two records: 
  
 WWW CNAME www.gentle-wind-.herokuapp.com 
 (http://www.gentle-wind-.herokuapp.com)
  
 URL CNAME gentle-wind-.herokuapp.com 
 (http://gentle-wind-.herokuapp.com)   # (I'm not sure if this one is 
 right/valid)
  
 The app is browsable at gentle-wind-.herokuapp.com 
 (http://gentle-wind-.herokuapp.com), but the redirected URL 
 (http://myapp.com) is giving me this message: 
  
 Heroku | No such app
  
 So I'm confused about how I should be setting this up. Usually I just do A 
 records that point to an IP, but after reading the article on heroku about 
 that I decided that an A record was not a good idea. So I'd like to set this 
 up with a www domain and a top level domain that redirects to www. How should 
 I set up my CNAME records to achieve this? 
  
 
  
 
 -- 
 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/-/uSGwjEBAFcoJ.
 To post to this group, send email to heroku@googlegroups.com 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: H12 Request Timeout

[Neil Middleton]

I'm not entirely sure what's causing your issues (as Richard said, raise a 
ticket) but there are a few things which stand out.

1) Your DNS is using the Heroku IPs - something which is now actively 
discouraged.

https://devcenter.heroku.com/articles/custom-domains#dns_setup

(I also wrote about this a while back:  
http://neilmiddleton.com/the-dangers-of-a-records-and-heroku/)

2) You appear to be serving static assets from your dynos.  I'm not sure what 
stack you're on, so you might be using Varnish, but as your requests are 
hitting your dynos I'd guess you're on Cedar.  If so, you really need to think 
about getting those assets off of your dynos and onto something like S3 / 
CloudFront.  Anything you can do to alleviate the HTTP requests onto they dynos 
is going to help.

N 

-Neil


On Monday, 2 April 2012 at 19:54, kowsik wrote:

 Neil,
 Just the odd timeouts.
 
 Thanks,
 
 K.
 ---
 http://blitz.io
 @k0ws1k
 
 On Mon, Apr 2, 2012 at 11:39 AM, Neil Middleton
 neil.middle...@gmail.com (mailto:neil.middle...@gmail.com) wrote:
  Kowsik,
  
  Are you seeing long queues or just the odd timeout?
  
  -Neil
  
  Sent with my tiny little Internet device.
  
  On Monday, 2 April 2012 at 19:22, Richard Schneeman wrote:
  
  I do you have rack cache on your app? I recommend setting that up and using
  memcache for the meta store. Also setting your expire headers on static
  assets to a far future date. That should help with timeouts especially with
  static assets. You can also try using a CDN but that is quite a bit more
  work for sinatra
  https://devcenter.heroku.com/articles/error-codes#h12__request_timeout
  
  You can also consider increasing your dyno count. What web server are you
  using?
  
  --
  Richard Schneeman
  http://heroku.com
  @schneems
  
  On Monday, April 2, 2012 at 12:27 PM, kowsik wrote:
  
  We are seeing sporadic H12 Request Timeout's in the logs, even for
  static assets:
  
  2012-04-02T17:25:06+00:00 heroku[router]: Error H12 (Request timeout)
  - GET blitz.io/images/logo.png dyno=web.1 (http://web.1) queue= wait=
  service=3ms status=503 bytes=0
  
  This is a Sinatra app on the Cedar stack. Given that this is a static
  asset, I'm pretty sure it's not our code or our database that's
  causing the problem.
  
  Any ideas?
  
  Thanks,
  
  K.
  ---
  http://blitz.io
  @k0ws1k
  
  --
  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 
  (mailto:heroku@googlegroups.com).
  To unsubscribe from this group, send email to
  heroku+unsubscr...@googlegroups.com 
  (mailto: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 
  (mailto:heroku@googlegroups.com).
  To unsubscribe from this group, send email to
  heroku+unsubscr...@googlegroups.com 
  (mailto: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 
  (mailto:heroku@googlegroups.com).
  To unsubscribe from this group, send email to
  heroku+unsubscr...@googlegroups.com 
  (mailto: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 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: Assets Precompile: Works Locally, Heroku Skips Some Files

[Neil Middleton]

I wonder if you have an exception that's being swallowed somewhere along the 
line.

- Have you tried running the assets:precompile with a --trace?
- Have you tried the same code on a new Heroku app / S3 bucket to rule out 
anything there?


-Neil


On Wednesday, 21 March 2012 at 16:08, Karl wrote:

 
 On Wednesday, March 21, 2012 6:38:20 AM UTC-7, Chap wrote:
  What do you mean by the files are sync'd to S3? 
 
  
  Are you using a library to put them on S3? By default they should just 
  remain in your slug and be served from there. 
  
 
 I have been using the asset_sync gem. I have tried allowing heroku to compile 
 the assets and sync on deploy. And I have compiled locally, including the 
 manifest.yml in the repo. Neither works.
  
  If so I might try removing that library and see if you still have the 
  problem. 
 
 Already tried that. Removing asset_sync gem doesn't make a difference. When 
 asset_sync is removed, it attempts to compile the assets, but doesn't 
 complete, give no error messages (console or logs), overwrites manifest.yml 
 with an empty array.
 
 Honestly, this shouldn't matter, because the builder should detect the 
 existing public/assets/mainfiest.yml files and not even attempt to compile 
 assets.
 
 I looked over the builder, and I don't see anything that stands out.
 
 BTW, I have several other heroku projects that I compile the assets locally 
 using asset_sync to sync with S3, include mainfest.yml in the repo, and it 
 works without fail.
  
  
  On Mar 20, 1:16 pm, Karl wrote: 
   On Tuesday, March 20, 2012 8:51:24 AM UTC-7, richard schneeman wrote: 
   
So if you bash into your application, are your files also missing from 
the dyno or can you see your the files? I'm curious if the files are 
not being generated correctly, or just not being synced correctly. 
   
$ heroku run bash 
Running bash attached to terminal... up, run.1 
~ $ ls public/assets 
application-95bd4fe1de99c1cd91ec8e6f348a44bd.css 
application.css   manifest.yml 
application-95bd4fe1de99c1cd91ec8e6f348a44bd.css.gz 
application.css.gzrails-782b548cc1ba7f898cdad2d9eb8420d2.png 
application-95fca227f3857c8ac9e7ba4ffed80386.js 
application.jsrails.png 
application-95fca227f3857c8ac9e7ba4ffed80386.js.gz 
application.js.gz 
   
What about your manifest.yml? 
   
   Yup, already tried that... manifest.yml is there. But... 
   
   
   
~ $ cat public/assets/manifest.yml 
rails.png: rails-782b548cc1ba7f898cdad2d9eb8420d2.png 
application.js: application-95fca227f3857c8ac9e7ba4ffed80386.js 
application.css: application-95bd4fe1de99c1cd91ec8e6f348a44bd.css 
   
   The manifest.yml is there, but the yaml is an empty array. What is 
   happening is heroku still *attempts* to compile assets, but borks, 
   overwrites my manifest.yml with a manifest.yml that is essentially an 
   empty 
   array (not an empty file, though). 
   
   Have you opened ahttps://support.heroku.comticket for this issue? 
   
   Yes. Been a week, the issue was escalated, but still no response. 
   Frustration ensues. 
   
   The only workaround I have it to turn assets.compile = true, and it 
   directs 
   the user to the assets on S3, but they are not compiled/combined/gzip'd. 
   
   Do you have any other ideas?
 
 -- 
 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/-/F6Kvelgv9pgJ.
 To post to this group, send email to heroku@googlegroups.com 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: Assets Precompile: Works Locally, Heroku Skips Some Files

[Neil Middleton]

Is your staging app setup with a staging env?  ie. RAILS_ENV and RACK_ENV are 
both staging?  

If not, you're going to be seeing some odd things with asset_sync. 

Neil


On Wednesday, 21 March 2012 at 17:33, Karl wrote:

 On Wednesday, March 21, 2012 9:18:26 AM UTC-7, Neil Middleton wrote:
  I wonder if you have an exception that's being swallowed somewhere along 
  the line.
  
  - Have you tried running the assets:precompile with a --trace?
 
 Yes. Both locally and on heroku.
 
 Locally, all assets compile without error.
 
 On heroku, no errors reported, nothing in logs, but as I have stated in 
 previous message, the manifest.yml is just an empty erray.
 
 FYI, the manifest.yml after asset:precompile on heroku:
 
  --- {}
 
 In the repo, it has all the correct assets.
 
 
  - Have you tried the same code on a new Heroku app / S3 bucket to rule out 
  anything there?
 
 No. I'll give it a try.
 
 Oddly enough, only the staging version of this app is giving me trouble. The 
 production version works as expected. So, in a way, I have tried it on a 
 different heroku account. Probably a good idea to try again.
 
 
  
  
  On Wednesday, 21 March 2012 at 16:08, Karl wrote:
  
   
   On Wednesday, March 21, 2012 6:38:20 AM UTC-7, Chap wrote:
What do you mean by the files are sync'd to S3? 
   

Are you using a library to put them on S3? By default they should just 
remain in your slug and be served from there. 

   
   I have been using the asset_sync gem. I have tried allowing heroku to 
   compile the assets and sync on deploy. And I have compiled locally, 
   including the manifest.yml in the repo. Neither works.

If so I might try removing that library and see if you still have the 
problem. 
   
   Already tried that. Removing asset_sync gem doesn't make a difference. 
   When asset_sync is removed, it attempts to compile the assets, but 
   doesn't complete, give no error messages (console or logs), overwrites 
   manifest.yml with an empty array.
   
   Honestly, this shouldn't matter, because the builder should detect the 
   existing public/assets/mainfiest.yml files and not even attempt to 
   compile assets.
   
   I looked over the builder, and I don't see anything that stands out.
   
   BTW, I have several other heroku projects that I compile the assets 
   locally using asset_sync to sync with S3, include mainfest.yml in the 
   repo, and it works without fail.


On Mar 20, 1:16 pm, Karl wrote: 
 On Tuesday, March 20, 2012 8:51:24 AM UTC-7, richard schneeman wrote: 
 
  So if you bash into your application, are your files also missing 
  from 
  the dyno or can you see your the files? I'm curious if the files 
  are 
  not being generated correctly, or just not being synced correctly. 
 
  $ heroku run bash 
  Running bash attached to terminal... up, run.1 
  ~ $ ls public/assets 
  application-95bd4fe1de99c1cd91ec8e6f348a44bd.css 
  application.css   manifest.yml 
  application-95bd4fe1de99c1cd91ec8e6f348a44bd.css.gz 
  application.css.gz
  rails-782b548cc1ba7f898cdad2d9eb8420d2.png 
  application-95fca227f3857c8ac9e7ba4ffed80386.js 
  application.jsrails.png 
  application-95fca227f3857c8ac9e7ba4ffed80386.js.gz 
  application.js.gz 
 
  What about your manifest.yml? 
 
 Yup, already tried that... manifest.yml is there. But... 
 
 
 
  ~ $ cat public/assets/manifest.yml 
  rails.png: rails-782b548cc1ba7f898cdad2d9eb8420d2.png 
  application.js: application-95fca227f3857c8ac9e7ba4ffed80386.js 
  application.css: application-95bd4fe1de99c1cd91ec8e6f348a44bd.css 
 
 The manifest.yml is there, but the yaml is an empty array. What is 
 happening is heroku still *attempts* to compile assets, but borks, 
 overwrites my manifest.yml with a manifest.yml that is essentially an 
 empty 
 array (not an empty file, though). 
 
 Have you opened ahttps://support.heroku.comticket for this issue? 
 
 Yes. Been a week, the issue was escalated, but still no response. 
 Frustration ensues. 
 
 The only workaround I have it to turn assets.compile = true, and it 
 directs 
 the user to the assets on S3, but they are not 
 compiled/combined/gzip'd. 
 
 Do you have any other ideas?
   
   -- 
   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/-/F6Kvelgv9pgJ.
   To post to this group, send email to heroku@googlegroups.com 
   (mailto:heroku@googlegroups.com).
   To unsubscribe from this group, send email to 
   heroku+unsubscr...@googlegroups.com 
   (mailto:heroku+unsubscr...@googlegroups.com).
   For more options, visit this group at 
   http://groups.google.com/group/heroku?hl=en.
  
 -- 
 You received this message

Re: External database connection via SSL

[Neil Middleton]

From looking at the injected database.yml (see bottom of 
http://neilmiddleton.com/sharing-databases-between-heroku-applications/) you 
can pass in extra configuration as part of the db URL as query params.  

In theory, this should let you configure it how you want although I've not 
tried it.  

-Neil


On Monday, 19 March 2012 at 16:53, Nathan Wenneker wrote:

 I'm running a Rails 3.2 app on the Cedar stack.
 
 I've successfully configured it to connect to an external Amazon RDS
 database using the appropriate DATABASE_URL config variable.
 
 However, I want my application to connect to the database via SSL.
 This would normally be configured in database.yml, but since Heroku
 generates this for me, I don't know how or where to specify the SSL
 option(s).
 
 Is this possible?
 
 Thanks!,
 
 Nathan
 
 P.S. I posted a question about this on stackoverflow a few days ago,
 but haven't seen much response to it, so I thought this list might be
 a better avenue. 
 http://stackoverflow.com/questions/9741072/specify-ssl-for-heroku-external-mysql-database-connection
 
 -- 
 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: heroku down (at least from Europe)

[Neil Middleton]

It seems EC2 went pop for a bit, all back now though.  

-Neil

Sent with my tiny little Internet device. 


On Thursday, 15 March 2012 at 09:40, marius wrote:

 Hello,
 
 For the past 5 minutes heroku (and sites hosted on it) is down from Europe:
 $ ping heroku.com
 PING heroku.com (50.19.85.156) 56(84) bytes of data.
 ^C
 --- heroku.com ping statistics ---
 21 packets transmitted, 0 received, 100% packet loss, time 1ms
 
 Looking forward to updates. 
 
 -- 
 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/-/Qlct7-PVaNgJ.
 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: Thoughts about this Forum

[Neil Middleton]

Personally, I think one list works.  Whilst there's some stuff that is getting 
more language specific, all of the questions are talking about the same 
underlying platform, and are therefore relevant to all to some extent.  
However, both here and on stackoverflow there are a lot of issues which are 
code specific, but only manifest themselves when running on Heroku hence the 
posting here (it's now a 'Heroku problem').

There's loads of issues (mainly on stackoverflow) that could be solved with 
simply testing your application in production mode locally first before 
pushing.  As people push then discover the issue, it get's the 'Heroku problem' 
tag.  I daren't guess what the Heroku support guys have to deal with here, it 
can only be ten times worse.

For the what it's worth, most of the conversations I've seen on here should 
stay. 

Neil


On Thursday, 15 March 2012 at 15:18, Tharnid wrote:

 Maybe its time to separate this group in to multiple mailing lists???
 
 On Thu, Mar 15, 2012 at 11:05 AM, Ed Jones ed.jo...@gmail.com 
 (mailto:ed.jo...@gmail.com) wrote:
  Not sure I understand all your post here.
  
  I use Cedar stack because I have a new-this-year rails app, which
  means RAILS 3.2, which means you need cedar (asset pipeline and all).
  Or so the docs led me to believe.
  
  I actually had not even noticed the other language posts; but now that
  I look back they are starting to build up. (In fact I didn't know
  Heroku had extended!)
  
  Maybe there needs to be a custom where you prepend the subject with
  [SCALA] or [FACEBOOK]?
  
  
  e
  
  On Mar 15, 10:42 am, Jeff Schmitz jeffrey.j.schm...@gmail.com 
  (mailto:jeffrey.j.schm...@gmail.com) wrote:
   I'm NOT complaining.
  
   I've just been thinking this, and wonder if I am alone, or are there 
   others
   who think/feel the same way or have solutions/suggestions
  
   I'm happy for Heroku to get an influx of new users on the Cedar stack.
Really, I am.  It is well-deserved, and even an exciting step to become a
   polyglot platform.  Developers using other languages deserve a platform
   like Heroku - probably need it even more than Ruby developers.
  
   However, I am a traditional Heroku user - Rails on Bamboo.  This forum has
   taught me a lot, about Heroku and Rails, and some Ruby.  I've tried to
   answer questions here and there, and help build this community.  I used to
   read every single post.
  
   This forum has changed now.  Messages about Rake files, or missing Gems, 
   or
   a other issues I can learn from or care about appear less and less, and 
   the
   discussion seems more about language-specific issues.  I could be wrong -
   haven't checked the stats or anything, but I do know this -
  
   I delete most messages from this forum in my inbox now.  They are about
   topics that don't impact me, and I cannot contribute to.  Please, new
   users, don't be offended, your posts help the Heroku community, we all
   understand that, and this is, indeed the place to ask them.  Post away.
  
   But asre bamboo users posting elsewhere, like Stack Overflow?
  
   Or is it just that Cedar is new, and its users are new, and therefore they
   have more questions?
  
   Am I being too picky?  Please respond and tell me so!
  
   Or prehaps have I become a LANGUAGE SNOB - Ruby or Death!
  
   Maybe I should just unsubscribe?
  
   Does anybody else share these feelings?  If so, any suggestions for the
   group?
  
   Does the google group need to be segmented by platform?  By language? How
   would this impact Heroku, who spends time patrolling this forum and 
   answers
   questions (Thanks a bunch for that)?
  
   Please tell me what you think - even if it's a cheerful Shut up and
   delete.
  
   jeff
  
  --
  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 
  (mailto:heroku@googlegroups.com).
  To unsubscribe from this group, send email to 
  heroku+unsubscr...@googlegroups.com 
  (mailto:heroku%2bunsubscr...@googlegroups.com).
  For more options, visit this group at 
  http://groups.google.com/group/heroku?hl=en.
  
 
 
 
 -- 
 { [Jeff] }
 
 http://www.jeffmsmith.me
 http://github.com/Tharnid
 
 -- 
 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 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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 

Re: Find out the name of the app I'm running on?

[Neil Middleton]

There's no direct way that I know of, however, if you're using NewRelic, you 
can see it in ENV[NEW_RELIC_APP_NAME] (assuming you've not renamed since 
setting it up).

The most foolproof way is exactly as you say, set your own key.

-Neil


On Wednesday, 14 March 2012 at 06:42, vierundsech...@googlemail.com wrote:

 This appears to be so simple that I feel a little dumb to ask it: Is there a 
 way to find out the name of the app? I'm currently using an 
 enviroment-variable that I set manually with heroku config:add 
 APP_NAME=my_awesome_app - but I guess there should be a better way?! 
 
 -- 
 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/-/CAhUXCZbAcQJ.
 To post to this group, send email to heroku@googlegroups.com 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: How can I save credentials for a subsequent heroku rake run?

[Neil Middleton]

The Heroku gem creates a credentials file in your home directory, so I'd start 
with replicating that. 

Neil



On 11 Mar 2012, at 13:26, dblock dblockdot...@gmail.com wrote:

 It seems that heroku rake wants more than just the SSH key setup on
 the client. We want to use this in automation and we keep getting
 these after a couple of days:
 
 04:46:45  [2012-03-11 05:46:45 -0400] bundle exec heroku rake ...
 04:46:50  /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/heroku-2.18.1/
 lib/heroku/helpers.rb:87:in `ask': undefined method `strip' for
 nil:NilClass (NoMethodError)
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/lib/heroku/auth.rb:96:in `ask_for_credentials'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/lib/heroku/auth.rb:137:in `ask_for_and_save_credentials'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/lib/heroku/auth.rb:71:in `get_credentials'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/lib/heroku/auth.rb:51:in `user'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/lib/heroku/auth.rb:11:in `client'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/lib/heroku/command/base.rb:38:in `heroku'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/lib/heroku/command/run.rb:74:in `rake'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/lib/heroku/command.rb:129:in `run'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/lib/heroku/cli.rb:9:in `start'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
 heroku-2.18.1/bin/heroku:15:in `top (required)'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/bin/heroku:
 19:in `load'
 04:46:50  from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/bin/heroku:
 19:in `main'
 04:46:50  Enter your Heroku credentials.
 04:46:50  Email: rake aborted!
 04:46:50  failed with exit code 1
 
 How can we save / store credentials so that this doesn't happen?
 
 -- 
 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: Keeping your Heroku app awake

[Neil Middleton]

To be brutally honest, there is no hard and fast rule, but I have found the 
following:

- Rails is really fast at slowing down, so ensure that your dependencies and 
initialisers are at an absolute minimum.

- Keep things small and lightweight, break your application up into lots of 
smaller applications. Sinatra, for instance, spins up almost instantly on 
Heroku and can take you a fair distance in terms of simple functionality

- Generally speaking, the newer the Rails version, the quicker the spinup time, 
especially if you're not using ActiveRecord

- If you're feeling beta-y, try running on Ruby 1.9.3, this makes a massive 
difference to Rails.

Other than this, I'm not really aware of any silver bullet, but I do know that 
lots of smaller more focused applications spin up better than one monolithic 
Rails app, which is why Unix is so good I guess. 

-Neil


On Monday, 20 February 2012 at 21:56, Ed Jones wrote:

 Neil said:
  I host loads of apps on 1 web dyno and just make sure that the spin up time 
  is short enough that it's not a problem.
 
 
 Neil and others, thanks.
 
 I just launched a new (beta) app, and the response time is just
 horrible.
 
 Could you pass a few tips on how to make sure that the spin up time
 is short enough?
 Thanks!!!
 
 ed
 
 
 On Feb 17, 7:48 am, Neil Middleton neil.middle...@gmail.com 
 (http://gmail.com) wrote:
  I'm confused here.
  
  The 'starter' package is only ~$35/mo which isn't exactly monumentally 
  expensive.  Are you suggesting something between that and free?
  What you're suggesting sounds like your charged by the CPU cycle rather 
  than the hours?
  
  To be brutally honest, I host loads of apps on 1 web dyno and just make 
  sure that the spin up time is short enough that it's not a problem.  If I 
  ever need to run more than 1 web dyno it's generally because the traffic 
  levels require it, in which case $35 becomes less of a problem.
  
  Personally, I think that having a single dyno, which can still serve 
  hundreds of thousands of requests a day /for free/ is a pretty good deal.  
  I'm happy to pay $35 to double it.
  
  Neil
  
  
  
  
  
  
  
  On Friday, 17 February 2012 at 12:44, Nick wrote:
   Peter,
  
  
   I take your points well. I don't mean to try and 'do one over' on
   Heroku. I appreciate the service you offer very much. My thinking
   behind it was that you would never exceed the 450 hours of dyno time
   allocated to each app so there wouldn't be a problem and if you did
   you would be charged anyway.
   
  
  
   Is there a paid for solution from Heroku to achieve the same result?
   The cost jump between 1 free dyno and paying for a dyno is quite large
   for small applications. So perhaps you could offer a $10 package which
   essentialy works the same way? If i'm honest I don't feel I pay Heroku
   enough but I have too many small apps (10 or so) to pay for each one
   to have a dedicated dyno.
   
  
  
   ?
   On Feb 16, 8:39 pm, Peter van Hardenberg p...@heroku.com 
   (http://heroku.com) wrote:
As a database guy at Heroku, I'm not one to speak authoritatively on
this, so please take this as the personal thoughts of someone and not
an official statement.

   
   
  
  
We idle apps in order to avoid having to charge for them. The more
people who prevent this behaviour, the more expensive our free apps
become to run, and the more likely we are to have to change our
policies about what we can offer in a free app.

   
  
  
While I admire the ingenuity in this post, I would suggest that you
reduce the amount of time your application takes to boot, or simply
accept that a few seconds of lag on the first request after a period
of idleness is a reasonable trade-off for free web hosting.

   
  
  
Peter
  
   --
   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 
   (mailto:heroku@googlegroups.com).
   To unsubscribe from this group, send email to 
   heroku+unsubscr...@googlegroups.com 
   (mailto: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 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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

Re: Resque on Cedar

[Neil Middleton]

See the comment from @hone about half way down.  This branch is working just 
fine for us in a few projects.

-Neil 

Neil


On Tuesday, 7 February 2012 at 17:30, kowsik wrote:

 We are planning on running resque (1.19.0) on cedar and saw this
 thread on orphaned workers:
 https://github.com/defunkt/resque/issues/319 Seems like there were a
 few proposed solutions, but no resolution yet.
 
 Is anyone else running resque on cedar? How do you work around the
 orphaned worker issue?
 
 Thanks,
 
 K.
 ---
 http://blitz.io
 @k0ws1k
 
 -- 
 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 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: Change app root directory or Procfile name using config vars

[Neil Middleton]

On Monday, 6 February 2012 at 20:16, Bradley wrote:

 So potential errors aren't the only concern.  If my API uses different 
 workers/process etc. from the App it becomes a bit onerous to define all 
 these different process types using config vars...
 

Sure, but remember that Heroku won't scale any of the other processes unless 
you ask it to.  You can easily declare all the other processes in the Procfile 
and scale them as needs be for each deployment of the application (so the names 
would need to be unique), only your web process would need to be configurable. 

For instance

web:  bundle exec $APP
worker_app1: bundle exec blah
worker_app2: bundle exec blah blah

etc
 Definitely don't want to split my code out (yet) if I can get away with it.  
 I wonder if anyone at Heroku can comment on this?  Presumably they have an 
 internal mechanism for finding the Procfile, it would be great if this was 
 configurable. 
If there is it isn't something that they mention in the docs (Process types 
are declared via a file named Procfile placed in the root of your app.) nor is 
it something that you really have control with with custom build packs (unless 
you want to get /really/ fruity).

-Neil 

-- 
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: How to becaome a full member to post messages to this list?

[Neil Middleton]

I can see this post - so I assume you've got everything you need... 

Neil


On Wednesday, 1 February 2012 at 15:53, Sev Gun wrote:

 Hi,
 
 I became a member of this group nearly a month ago but my message is not 
 still showng on list and I have no feedback about it.
 
 Can you please tell me what to do to be able to post messages directly?
 
 We are starting development soon and I want to ensure we can ask for help 
 when needed during project
 
 Thanks
 Sevgi Guner
 -- 
 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 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: European clients hosted on Heroku?

[Neil Middleton]

I cannot remember the specifics of the EU directive off hand as to whether
or just applies to storage of the data or whether it's not pertaining to
the storage AND communication of the data (just like PCI for instance).

If it's just storage, bear in mind that you don't have to use the Heroku
databases if you don't want to.  You could use anything which is hosted
directly on EC2 (as Amazon IS Safe Harbor certified).  You've Amazon RDS
(If you're not bothered by MySQL), you've got many AMI's out there
featuring Postgres, and I dare say some other options too.

Obviously this doesn't help you if you want to stick everything onto the
Heroku platform, but it does mean that you have options which doesn't stop
you from using the slick Heroku deployment and management - it's the data
that cannot make use of the Heroku platform.

I know Heroku are still working on Safe Harbor ceritfication, but it isn't
a small thing and will take time.

Neil

On Thu, Jan 26, 2012 at 11:33 AM, Rich Aston r...@futuremill.co.uk wrote:

 We hit exactly this problem. The legal advice we got was explicit: EU
 companies can not host any personal data with Heroku as it stands.
 There are two potential solutions:

 1. Heroku could sign up to Safe Harbor.
 2. They could offer EU based servers.

 When I spoke to them about this last year they were hoping to be
 signed up to Safe Harbor by the end of 2011, but they missed this and
 I've been given no new date that they are aiming for. In the end we
 had to move to Engine Yard (who are both Safe Harbor compliant and
 offer EU servers) and this is working out pretty well for us. But we
 would love the option to come back to Heroku.

 Rich



 On Dec 18 2011, 12:06 pm, Nicola Brisotto nicolabriso...@gmail.com
 wrote:
  Hi!
  Do you have any news on this topic?  When Heroku will become members of
  Safe Harbor?

 --
 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.




-- 
Neil

-- 
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: Interactive console on Cedar

[Neil Middleton]

heroku run console is fine on the cedar stack.

Neil


On Tuesday, 10 January 2012 at 15:11, Scott LaBounty wrote:

 Try just heroku console.
 
 Scott
 
 On Tue, Jan 3, 2012 at 2:46 PM, Martin Aspeli optil...@gmail.com 
 (mailto:optil...@gmail.com) wrote:
  Hi,
  
  I feel like I'm missing something really basic here, but... Reading
  the docs, I had expected to get to an interactive console by doing:
  
  $ heroku run console
  
  However, this just does:
  
  $ heroku run console
  Running console attached to terminal... up, run.1
  
  It exits with nothing more. What am I missing?
  
  Martin
  
  --
  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 
  (mailto:heroku@googlegroups.com).
  To unsubscribe from this group, send email to 
  heroku+unsubscr...@googlegroups.com 
  (mailto:heroku%2bunsubscr...@googlegroups.com).
  For more options, visit this group at 
  http://groups.google.com/group/heroku?hl=en.
  
 
 
 
 -- 
 Scott
 http://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 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: Platform errors

[Neil Middleton]

 To be honest I think most of the time they're pretty much aware if it's
something thats affecting the stack.

From what I understand of the monitoring systems, Heroku have an 'expected'
error rate across the stack.  When this moves to something above a certain
threshold then the ops will look into it (hence the 'elevated error rates'
incidents).  This could be anything, for instance, errors on the Facebook
API will then cause Heroku's 800,000-odd applications to start throwing
more exceptions that normal thus causing an incident to be raised.

Saying this though, I'm unsure as to what latency there is between the
event and the incident appearing on status.heroku.com.  I'd like to think
that it's not long, but that they're also more focused on fixing the issue
rather than updating their status site.

Neil

On Tuesday, 10 January 2012 at 22:03, Mike Abner wrote:

 Yeah. In the past I've created support issues when I've noticed the status
as OK but errors on my apps.  I'd like to see a lighter way of letting them
know.  I figured responding to the newsgroup might also get their
attention.

Mike

On Tuesday, January 10, 2012 at 1:43 PM, John Beynon wrote:

pressed enter too quickly -

I meant to finish it off with

'sometimes it takes a while to be updated - it could be your failures are
triggering errors at heroku which they will be picking up on'

-- 
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/-/wVxk-m-hSLcJ.
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: Platform errors

[Neil Middleton]

On Tue, Jan 10, 2012 at 10:44 PM, Mike Abner mike.ab...@gmail.com wrote:


 The question though, from where I sit, is if my apps are having trouble,
 does that trigger enough of an elevated state for them to look into it,
 or do I need to be explicit about pinging support with a ticket saying i'm
 having an issue.


It can't hurt, although I tend to leave it for a few minutes and try a few
simple DIY fixes such as restarts, check logs etc first.

-Neil

-- 
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: @Heroku: How about some help here?

[Neil Middleton]

There are some heroku staffers who dip in and out every now and then answering 
stuff when necessary but the bulk of questions get answered.

I dare say a lot of stuff on here ends up in the Heroku support system, or 
elsewhere such as StackOverflow. 

Neil


On Friday, 23 December 2011 at 11:15, djangst wrote:

 @Heroku,
 
 This may not be intended as an official support channel, but how about
 assigning someone to hang out here and answer questions? Many
 questions here go unanswered, and that isn't only recently.
 
 Even if the answer is just to read the documentation, or contact
 Support directly, or Sorry, can't help with that one, it's better
 than nothing.
 
 It looks bad. Don't you guys have a bunch of money now? ;)
 
 -- 
 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 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: @Heroku: How about some help here?

[Neil Middleton]

But where should Heroku draw the line - should they also hang out on 
Stackoverflow?  Should they also hang out in IRC 24/7?  There's only so much 
resource, and that's focused on the direct customer support channel as far as I 
can see.

I have seen many responses from Heroku in the past. 

Neil


On Friday, 23 December 2011 at 11:23, djangst wrote:

 Out of the last 90 threads, 49 have 1 message (no response).
 
 You answer questions here, but the lack of responses from Heroku is
 noticeable.
 
 I can't imagine there's a no response policy to get people to move
 questions into the support system, but if there were, it's a bad
 tactic.
 
 On Dec 23, 6:17 am, Neil Middleton neil.middle...@gmail.com 
 (http://gmail.com) wrote:
  There are some heroku staffers who dip in and out every now and then 
  answering stuff when necessary but the bulk of questions get answered.
  
  I dare say a lot of stuff on here ends up in the Heroku support system, or 
  elsewhere such as StackOverflow.
  
  Neil
 
 -- 
 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 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: heroku rake db:migrate - Internal Server Error

[Neil Middleton]

Status.heroku.com has just shown tool errors. Sounds like a platform issue. 

-Neil. 

On 22 Dec 2011, at 22:45, John McCaffrey john.mccaff...@gmail.com wrote:

 I used to just get 'internal server error' in the console when I had various 
 syntax issues, until i updated to the latest heroku gem, now I see more 
 useful info.
 
 See if that helps your migration.
 
 Does your migration work locally? Is it complex? (eg. doing something more 
 than just changing table def)
 
 On Thu, Dec 22, 2011 at 4:25 PM, Scott LaBounty slabou...@gmail.com wrote:
 I'm seeing this ...
 
 
 $heroku rake db:migrate --trace
  ! !Internal server error.
  ! !Run 'heroku status' to check for known platform issues.
 $ heroku status
 
 All Systems Go: No known issues at this time.
 
 
 Should I just try later or is something else wrong that I should look at?
 
 -- 
 Scott
 http://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.com.
 For more options, visit this group at 
 http://groups.google.com/group/heroku?hl=en.
 
 
 
 -- 
 Thanks,
 -John
 
 -- 
 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: Background job guidance

[Neil Middleton]

The only thing I've seen worth mentioning is that Heroku recommend using this 
fork of Resque:

http://github.com/hone/resque.git

In particular the keepalive branch.  I'm unclear as to why. 

Neil


On Thursday, 8 December 2011 at 14:46, Chap wrote:

 Delayed Job has long been supported on heroku and I've had no issues
 with it.
 
 Here's a couple of docs I would recommend you read:
 http://devcenter.heroku.com/articles/queueing
 http://devcenter.heroku.com/articles/delayed-job
 
 (It does seem that resque is the new favorite in the rails community,
 but I have yet to give it a try because dj is so darn easy and hasn't
 failed me yet.)
 
 On Dec 7, 7:53 pm, djangst djan...@gmail.com (http://gmail.com) wrote:
  Hi, I'm looking for current advice on running background jobs on
  Heroku, most likely for a Rails app.
  
  Are there any particular gotchas to be aware of?
  
  Is there a preferred option among those available, such as Resque?
  
  Anything else? 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 
 (mailto:heroku@googlegroups.com).
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com 
 (mailto: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: Anyone else have a problem with status.heroku lack of information?`

[Neil Middleton]

But does it matter?

For me it's good to know there's something up if I'm seeing odd behaviour,
even though I can't do anything about it.

After two years of using Heroku, I've never seen an issue on status that I
can fix, and generally don't care what the problem is other than knowing
that Heroku are learning from it, and out of idle interest.

Saying that, when things have gone bad, for instance when EC2 blew up last
year, heroku have always posted a detailed synopsis...

N
On Dec 5, 2011 10:06 PM, daudi dsaro...@gmail.com wrote:

 There seems to be almost zero information content at
 status.heroku.com. Does anyone have a better parser than mine? The
 general posting format seems to be:

 posting @ t[0]:
 ISSUE: We are observing increased [ server | HTTP | network | database
 | routine] error [ rates (and | or) latencies ] to [ applications |
 the Heroku API ]. We are investigating and will post additional
 updates as we learn more.

 n-2 postings @ t[i]:
 ISSUE: We are continuing to work on resolving the [ server | HTTP |
 network | database | routing]  issues.
 [
  Applications are largely up |
  the problems are largely isolated to our something obscure |
  except for an extremely small number of requests |
  problems seem to be isolated to intermittent problems with
 something obscure |
  it's really not such a big deal at all and we can't understand why
 so many of you are even looking at status.heroku.com right now but
 we'll write something reassuring here anyway
 ], but we are still experiencing some performance degradation.  We are
 working to resolve this problem as quickly as possible.

 nth (and final) posting hours/days later @ t[n]:
 We believe the incident is now entirely resolved. Error rates have
 returned to nominal levels. We will continue to monitor the platform
 and HTTP stack very closely, but at this time are discontinuing
 tracking of this incident.

 Missing are the specifics:
 what really happened? how bad was it? what broke? why? what fixed it?

 -- from a fan/customer/supporter of heroku

 --
 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: Can I issue a heroku restart from within my app that's running on Heroku?

[Neil Middleton]

You can always use the Heroku gem to talk to the heroku infrastructure as the 
CLI does.

For instance:

@heroku = Heroku::Client.new(ENV[HEROKU_EMAIL], ENV[HEROKU_PASSWORD])

You can then issue commands such as:

@heroku.restart('app_name')

Neil

On 15 Nov 2011, at 21:56, Corey Trager wrote:

 I have been doing the logs --tail.
 
 A little more info.  My Heroku app screen scrapes another website.
 For reasons I don't understand, HTTP::Net.get_response sometimes
 results in EOFError and once that happens once, it happens always.
 It's as if somewhere deep in the ruby libs, there's some state that
 gets messed up and I don't know how to clear.   Or maybe it's
 something in Heroku's infrastructure that's messed up that restarting
 clears.  I don't know.   Googling HTTP::Net and EOFError results in
 stories that are similar, but not exactly the same.
 
 I can try/rescue and catch the error, but that doesn't help clear that
 messed up state.
 
 I could run a cron job on my dev machine and issue heroku restart
 from there, but that's what I'm trying to avoid.
 
 On Nov 15, 2:18 pm, John McCaffrey john.mccaff...@gmail.com wrote:
 I'm interested in that as well, but if the answer ends up being 'no',
 perhaps your app could just capture the current state (eg. what caused it)
 and send out an alert.
 
 when I've had problems in the past, I've been helped by
 logging (logs --tail and the loggly add on)
 new relic
 exception notification
 google analytics (see traffic patterns and urls)
 
 If you see the pattern and can fix it, you won't need to do the restart
 business.
 
 
 
 
 
 
 
 
 
 On Mon, Nov 14, 2011 at 11:06 PM, Corey Trager ctra...@gmail.com wrote:
 My app gets into a bad state for reasons I haven't figured out yet.
 So far, the only solution I've found is to issue a heroku restart
 command.  The app itself can detect the bad state and so I'd like the
 app itself to issue the restart.  Is that possible?   It's a Sinatra
 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.
 
 --
 Thanks,
 -John
 
 -- 
 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.

Cedar migrations

[Neil Middleton]

Anyone able to help with this conundrum?

ruby-1.9.2  ~/code/rest_test (master)  ➔ heroku rake db:migrate

 !   For Cedar apps, use: `heroku run rake db:migrate`

ruby-1.9.2  ~/code/rest_test (master)   ➔ heroku run rake db:migrate

Unknown command. Run 'heroku help' for usage information.


TIA

Neil

-- 
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/-/a7ReE904f4YJ.
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: European clients hosted on Heroku?

[Neil Middleton]

I was of the understanding that as Heroku is on EC2, and Amazon *are*members of 
the Safe Harbor agreement, that all was well.

-- 
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/-/zOKKJK3H_r8J.
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: NewRelic Real User Monitoring

[Neil Middleton]

I can see it in my NewRelic reports - but as yet I've not had any data appear 
for the app that I've upgraded the agent one (and that was some hours ago)

N
On Tuesday, 17 May 2011 at 15:29, szh wrote: 
 I am using the NewRelic Bronze addon in my Rails 3 app on Heroku. Will 
 NewRelic's new Real User Monitoring 
 (http://support.newrelic.com/kb/features/new-noteworthy) be available? 
 
  -- 
  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: Cron addon has been failing to run

[Neil Middleton]

We've only got one, but yes, that missed it's run this morning.


Neil Middleton
http://about.me/neilmiddleton

On Monday, 16 May 2011 at 14:21, nevinera wrote: 
 On several of our servers, we use the hourly cron addon to schedule delayed 
 jobs, but it stopped running sometime early this morning. Nobody on our end 
 has touched the servers at all since Friday. Is anybody else having Cron 
 issues this morning? 
 
  -- 
  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.
 
 Attachments: 
 - late-cron.png
 
 

-- 
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: Wildcard AddOn

[Neil Middleton]

Have you added the wildcard domain to the app?
On Apr 25, 2011 3:19 PM, Scott Watermasysk scottwa...@gmail.com wrote:
 Any tips for setting up the wildcard addon? When I try to visit a
subdomain off of my main url, I get a the heroku No Such App page.

 My setup steps:

 1. Add the addon
 2. configure DNS (created a cname for * and pointed to proxy.heroku.com
 3. executed host mysub.mydomain.com

 I am not sure using proxy.heroku.com is correct in step #2, but the docs
http://devcenter.heroku.com/articles/custom-domains are not very clear on
that point.

 Thanks,
 Scott

 --
 Scott Watermasysk
 Founder, KickoffLabs
 http://kickofflabs.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.

Re: No way to access any part of Heroku

[Neil Middleton]

or even Europe ;)


Neil Middleton
http://about.me/neilmiddleton

On Thursday, 21 April 2011 at 17:02, kowsik wrote: 
 Is there a reason why Heroku doesn't spread the dynos across us-west-1
 and us-east-1?
 
 K.
 ---
 http://blitz.io (down at the moment)
 http://twitter.com/pcapr
 
 On Thu, Apr 21, 2011 at 8:50 AM, Rohit Dewan dew...@gmail.com wrote:
  According to Amazon, the N. Virginia cluster is the one experiencing an
  outage.
  Does anyone know why Heroku not able to redeploy onto another cluster? In
  general, it would seem prudent to spread applications across the various
  clusters so all apps do not suffer an outage when a single cluster is
  affected.
  - Rohit
  
  On Thu, Apr 21, 2011 at 8:47 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com
  wrote:
   
   Curiously, my site was up for a long time during theses issues but is now
   down.
   Do we know exactly which of the red line items
   on http://status.aws.amazon.com/?a are the cause?
   jeff
   On Thu, Apr 21, 2011 at 10:39 AM, Steve Smith st...@scsworld.co.uk
   wrote:

It is Pito, we're in the UK so we've been up a while we have, been
watching this for a while now. Unfortunately things have been playing 
up on
AWS for a quite a few hours. I think there will be some questions for 
Amazon
once things are resolved.

On 21 Apr 2011, at 16:24, Pito Salas pitosa...@gmail.com wrote:

 I wonder if it has anything to do with this:
 http://status.aws.amazon.com/?a
 
 -- Pito
 
 On Thu, Apr 21, 2011 at 11:08 AM, Steve Smith st...@scsworld.co.uk
 wrote:
  Rohit, These issues are affecting pretty much everyone on the EC2
  US-East
  region. It's actually something out of Heroku's hands. If you take a
  look at
  the news there are many large scale sites down. A lot of our stuff 
  is
  down
  too (although fortunately a lot of our core stuff is also hosted in
  multiple
  locations).
  
  --
  Steve Smith
  @cloudmailin
  http://cloudmailin.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.
 
 
 
 --
 Check out http://www.salas.com and http://www.blogbridge.com/look
 
 --
 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.
 
 -- 
 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.

Odd problem with distance_of_time_in_words

[Neil Middleton]

I have a Rails 3.0.5 app that uses distance_of_time_in_words to show some 
timestamps:

= #{distance_of_time_in_words(note.created_at.localtime.to_time, 
Time.zone.now)} ago

However, in dev, it works fine, but on Heroku, I'm getting consistently wrong 
values returned. For instance, where the dev env will return the values 20 
hours ago, 1 day ago etc, Heroku's version will return 'less than a minute ago' 
for both (some others vary by a minute or so).

So. Question is WTF? The timestamps in the data are correct (and the same 
between dev and production).

Time.now on Heroku is returning: Wed Apr 06 11:31:46 +0100 2011
Time.zone.now on Heroku is returning: Wed, 06 Apr 2011 10:31:46 UTC +00:00

Locally, the same values are:

Wed Apr 06 11:31:46 +0100 2011 and Wed, 06 Apr 2011 10:31:46 UTC +00:00

Any ideas?

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.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Re: Dynonamics: Auto-scaling your dyno. Alpha testing users needed!

[Neil Middleton]

Not trying to be funny or anything, but this looks suspiciously like it's 
trying to be Heroku proper, and not just an app hosted on Heroku.

This would put me off straight away... 

Neil Middleton
http://about.me/neilmiddleton
On Wednesday, 6 April 2011 at 14:50, Tanin wrote: 
 Hello Heroku users,
 
 Dynonamics adjusts your dynos automatically according to your
 website's traffic.
 
 I'm looking for medium-sized Rails applications that requires more
 than 3-4 dynos to do Alpha testing.
 
 You can see more information here: http://dynonamics.heroku.com/help
 If anyone is interested, please send me an email: tani...@gmail.com
 
 Regards,
 Tanin Na Nakorn
 http://www.whowish.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.

Re: Problem with heroku logs

[Neil Middleton]

Are you running an up to date version of the gem?


Neil Middleton
http://about.me/neilmiddleton
On Friday, 11 March 2011 at 16:21, Dave wrote: 
 Hi,
 
 I have many Heroku sites, and the command line heroku logs works for
 most of them. One in particular though echoes back This feature is
 not supported by your client version. No idea why
 
 What is mis-configured for this site? Any usual suspects I can check?
 
 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.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: H12 errors, blocked dynos and Heroku website claims.

[Neil Middleton]

The dyno is still running the long request, successfully. It's only the routing 
mesh that's returned the timeout error back to the user. Therefore, the dynos 
still in your 'grid' and ready for new requests.

I blogged about something very similar a couple of weeks back: 
http://neilmiddleton.com/avoiding-zombie-dynos-with-heroku 

Neil Middleton
http://about.me/neilmiddleton
On Wednesday, 16 February 2011 at 16:42, Tim W wrote: 
 The Heroku website claims:
 
 http://heroku.com/how/dyno_grid_last#3
 If a dyno is unresponsive for any reason (user bugs, long requests,
 or high load), other requests will be routed around it.
 
 In my experience, this does not seem to be the case. We have several
 admin features in our app that when requested with certain params, it
 can take longer then 30s to run. (I am working on ways to get these in
 check and in the background). When a user trips one of these long
 running requests, Heroku appears to queue additional requests to this
 dyno and those requests time out, even though there are plenty of
 other dynos available to handle that request.
 
 Is the statement on the Heroku website true or false? It does not
 appear that Heroku actively monitors the dynos to see if they are busy
 with a long running request. Is there a better way to handle this
 situation?
 
 Thanks..
 -tim
 
 -- 
 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: No-downtime deployment to Heroku?

[Neil Middleton]

As I understand it from the many hundreds of deploys I've done over the last 
year or so that everything cycles at once. The new app is built 'offline' and 
then swapped in capistrano style.

If you weren't using MondoDB you would have to worry about the gap between a 
slug being compiled and the migrations finishing. 

Neil Middleton
http://about.me/neilmiddleton
On Wednesday, 16 February 2011 at 16:45, dblock wrote: 
 I am looking at building a production environment for continuous
 deployment to Heroku.Traditionally we did this with two (or more)
 servers and some load-balancer in front of it. We'd take one server
 out, push code, bring it back in. Then we'd repeat with the second
 server. Am I correct that this is not necessary with Heroku (or it
 does that for me)?
 
 I'd like to understand what happens during deployment from the request
 point-of-view. Lets say I have N dynos and am pushing new code. When
 does the application get swapped? Is there any request downtime?
 
 We're backed by MongoDB, so we have no data migrations. The old code
 works with the database and the new code works with the same database.
 We can be careful about (re)saving data so that the old version
 doesn't break.
 
 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 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: H12 errors, blocked dynos and Heroku website claims.

[Neil Middleton]

Although the symptoms that you are seeing may not indicate it the two systems 
are the same. There is a queue backlog, and the dynos pick up the next request 
from that backlog when they become idle, as described here: 
http://devcenter.heroku.com/articles/key-concepts-performance (esp the part 
about backlog).

I've seen many instances on my applications which indicate this to be an 
accurate description.

Although I have no real clue about the application you have regarding number of 
dynos etc, it would appear that what you are seeing could be a different 
problem. 

Neil Middleton
http://about.me/neilmiddleton
On Wednesday, 16 February 2011 at 18:01, Tim W wrote: 
 It is not identical to what Heroku is providing.. The Heroku mesh
 seems to blindly sends a request to a dyno, no matter the current
 status of the dyno. The queue is at the dyno level. Passenger holds
 back the request until a process is available..
 
 With passenger you do not end up in the situation noted below, where
 as with Heroku you do..
 (Request Y gets served ok with passenger, with Heroku, request Y gets
 the H12 error)
 
 Quoted from passenger docs (this is what happens if you have that
 feature turned off on passenger and what always happens with Heroku):
 --
 The situation looks like this:
 
 Backend process A: [* ] (1 request in queue)
 Backend process B: [*** ] (3 requests in queue)
 Backend process C: [*** ] (3 requests in queue)
 Backend process D: [*** ] (3 requests in queue)
 Each process is currently serving short-running requests.
 
 Phusion Passenger will forward the next request to backend process A.
 A will now have 2 items in its queue. We’ll mark this new request with
 an X:
 
 Backend process A: [*X ] (2 request in queue)
 Backend process B: [*** ] (3 requests in queue)
 Backend process C: [*** ] (3 requests in queue)
 Backend process D: [*** ] (3 requests in queue)
 
 Assuming that B, C and D still aren’t done with their current request,
 the next HTTP request - let’s call this Y - will be forwarded to
 backend process A as well, because it has the least number of items in
 its queue:
 
 Backend process A: [*XY ] (3 requests in queue)
 Backend process B: [*** ] (3 requests in queue)
 Backend process C: [*** ] (3 requests in queue)
 Backend process D: [*** ] (3 requests in queue)
 
 But if request X happens to be a long-running request that needs 60
 seconds to complete, then we’ll have a problem. Y won’t be processed
 for at least 60 seconds. It would have been a better idea if Y was
 forward to processes B, C or D instead, because they only have short-
 living requests in their queues.
 
 
 
 
 On Feb 16, 12:50 pm, Neil Middleton neil.middle...@gmail.com wrote:
  Is this not identical to what Heroku provides though? Your global queue is 
  your applications dynos and the routing mesh will send requests to 
  whichever dynos are idle. The wait being the backlog.
  
  The only difference I can see is that Passenger won't, by default, spit 
  back any requests that take longer than 30 seconds.
  
  Neil Middletonhttp://about.me/neilmiddleton
  
  
  
  
  
  
  
  On Wednesday, 16 February 2011 at 17:46, Tim W wrote:
   Passenger... imho handles this better then Heroku
  
   http://www.modrails.com/documentation/Users%20guide%20Apache.html#Pas...
  
 If global queuing is turned on, then Phusion Passenger will use a 
 global queue that’s shared between all backend processes. If an HTTP 
 request comes in, and all the backend processes are still busy, then 
 Phusion Passenger will wait until at least one backend process is 
 done, and will then forward the request to that process.
  
   default is on
  
   On Feb 16, 12:36 pm, Neil Middleton neil.middle...@gmail.com wrote:
AFAIK Passenger does have a similar concept with running processes 
(having a default of six running processes, which are comparable to 6 
dynos).
  
The situation you describe should have the same results on Passenger as 
Heroku. More info on Passenger 
here:http://www.modrails.com/documentation/Users%20guide%20Apache.html#_re...
  
Neil Middletonhttp://about.me/neilmiddleton
  
On Wednesday, 16 February 2011 at 17:29, Tim W wrote:
 I guess I am just used to using passenger which uses a global queue,
 making a single long running request a non issue.
  
 On Feb 16, 11:57 am, Neil Middleton neil.middle...@gmail.com wrote:
  Is it, but you have a healthy dyno. If the dyno crashes, or hangs 
  somehow, it gets removed.
  
  Neil Middletonhttp://about.me/neilmiddleton
  
  On Wednesday, 16 February 2011 at 16:55, Tim W wrote:
   Thanks, I will give rack-timeout a try.
  
   So what it seems like is that the routing mesh is not as 
   sophisticated
   as Heroku leads on?
  
   On Feb 16, 11:45 am, Neil Middleton neil.middle...@gmail.com 
   wrote:
The dyno is still running

Re: Bundles add-on deprecation

[Neil Middleton]

Do you have your code in a git repo external to Heroku at all? If so, surely 
this is a backup of the code?

As Heroku as a read only filesystem, data should be the only thing in 
production which you don't already have a copy of. 

Neil Middleton
http://about.me/neilmiddleton
On Tuesday, 15 February 2011 at 23:38, Wes Gamble wrote: 
 I was using the bundles add-on to do backups of each of my Heroku apps., but 
 I see that as of today, bundles are deprecated. 
 
  pgbackups is mentioned as a replacement.  I'm already using pgbackups to do 
 database backups.
 
  However, pgbackups isn't really a full replacement for the bundle add-on, 
 since it only backs up the DB, and not any files, nor the git repo. of the 
 app.
 
  What is the recommended way to do file backups and git repo. backups given 
 the deprecation of bundles?
 
  Also, all of my apps. still show the bundle add-on as installed - do I have 
 to remove it myself or will it eventually disappear?
 
  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.

Re: Your application is too busy to open a console session.

[Neil Middleton]

This had me worried for a minute, as I frequently open consoles on 1 dyno apps. 
That message suggests that if a console is open, a dyno is busy servicing the 
request.

However, after a quick check it seems to not be the case. Maybe someone @ 
Heroku could tell us what the deal is here - I don't want my inquisitiveness to 
take a site offline ;)


Neil Middleton
http://about.me/neilmiddleton
On Saturday, 12 February 2011 at 12:14, MikeBlyth wrote: 
 Console sessions require an open dyno to use for execution. 

-- 
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: rails 3.0.4

[Neil Middleton]

Upgrade and push - it's only bundler updates that Heroku might need to do
something about first.

On Wed, Feb 9, 2011 at 3:24 PM, Josh Coffman joshcoff...@gmail.com wrote:

 Thanks! I was thinking it would get resolved by Bundler, but didnt want to
 push out my app and find out I was wrong. I'll give it a try.



 On Wed, Feb 9, 2011 at 7:41 AM, Steve Smith st...@scsworld.co.uk wrote:

 Unless I've missed something there's rarely a reason why you can't just
 update your app and push to Heroku.

 --
 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.




-- 
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.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Re: Scaling - Big and Fast

[Neil Middleton]

Not us, someone else.

From what I gather, at 7am they were doing ~5m hits per hour.
On Feb 3, 2011 8:26 PM, John Norman j...@7fff.com wrote:
 You had 1666+ requests/second, and had to bring in several hundred
 more EC2 instances?

 Those numbers seem off.

 On Thu, Feb 3, 2011 at 8:08 AM, Neil Middleton neil.middle...@gmail.com
wrote:
 This week in the UK we had the launch of police.uk, an Django based site
 hosted on EC2.  Pretty much straight away it went down through load.
 From
 talking to the developers, it transpires that they were seeing 100,000+
 requests per minute, and had to draft in several hundred more EC2
instances
 to cope.
 Which leads me to a tasty hypothetical question.  If for instance I
wanted
 to launch a site like that on Heroku, are there any limits to where you
can
 scale too and how long it might take?  I know from experience that I can
get
 50 dynos within a couple of seconds, but surely there must be a point
where
 this is a little harder to provision?  Are there any known limits?  What
 happens if I want, say, 5000 dynos right now?  At what point does the DB
 layer start to suffer?  How would Heroku handle a site of this magnitude
 appearing 'all of a sudden'?

 --
 Neil Middleton
 http://about.me/neilmiddleton
 The internet's most comprehensive source for all things Neil Middleton

 --
 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 heroku%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: Hanging when creating new Heroku app?

[Neil Middleton]

http://status.heroku.com/

On Fri, Jan 21, 2011 at 4:53 PM, Mike Abner mike.ab...@gmail.com wrote:

 Last night there was downtime for app creation.  Maybe it isn't fully
 resolved (thought there was a follow up tweet that it was fixed).

 Wouldn't hurt to ping support.

 Mike


 On Thu, Jan 20, 2011 at 11:40 PM, Mal leyndur...@gmail.com wrote:

 I've created several Heroku apps before, but now when I try, it's
 stuck creating it forever:

 ~$ heroku create
 Creating strong-

 dawn-106.

 (Forever as in it's been going for two hours now, so there are a very
 large number of dots.)

 Has anyone been having this issue? I recently finally upgraded to OS X
 Snow Leopard (after being previously on Leopard), not sure if that has
 anything to do with it. I tried uninstalling and reinstalling the
 heroku gem, but no dice. I'm not really sure what heroku create does
 -- can I do whatever it does some other way? The strong-dawn-106 app
 does appear in my list of apps on heroku.com, so maybe I just need to
 add heroku as a git repo?

 --
 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.comheroku%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/heroku?hl=en.




-- 
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.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Security vulnerability

[Neil Middleton]

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.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Re: Changing an application when not an owner

[Neil Middleton]

 I've seen Herogit before, but haven't tried it since the credentials support 
went - I'll have a look






Neil Middleton
http://about.me/neilmiddleton


On Tuesday, 4 January 2011 at 16:59, Keenan Brock wrote:

 Neil,
 
 
 You may want to check out this article:
 
 
 http://getsatisfaction.com/heroku/topics/can_i_use_different_heroku_credentials_on_different_projects
 
 
 Please share if any of those suggestions work for you.
 
 
 --Keenan
 On Jan 4, 2011, at 11:50 AM, Neil wrote:
 
 
  Back when the Heroku gem used a credentials file, we were able to change 
  our 'user' from the command line so that we could interact with different 
  apps (we have all our apps on a company account, but locally use our own 
  accounts via collaboration)
  
  
  Question is, given that the credentials file is now gone, how can we we 
  'sudo' up to the app owner in order to make changes? Is there an easy way 
  of changing user in the Heroku gem?
  
  
   -- 
   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: Some Heroku questions

[Neil Middleton]

Use the heroku_san gem...
On Dec 30, 2010 6:09 PM, Steve Smith st...@scsworld.co.uk wrote:
 I personally set up two branches just in case we every have to make a hot
fix. So we create two branches and two remotes (live and staging) and then
say something like:

 $ git push staging staging:master

 to push the staging branch to the staging remote or

 $ git push live master

 to push the master branch. Using this method also stops me from 'habit
typing' origin or heroku master and pushing to the production site
accidentally which is amazingly easy to do with heroku being so easy to
deploy to. I know there are others who use rake tasks and scripts to help
them handle deployment though.


 On 30 Dec 2010, at 17:48, Josh Coffman wrote:

 As far as staging, I have a separate heroku app for that. I just git
push test master for staging or git push live master for live. works well
for me at least.


 On Thu, Dec 30, 2010 at 9:57 AM, Wes Gamble we...@att.net wrote:
 To piggyback on this question - how do people handle staging vs. live? Do
you point at the same repo. but use different branches to deploy, or
something else?

 Wes

 On 12/30/10 7:35 AM, femto Zheng wrote:

 Yes, that's it, thanks for the info.


 On Thu, Dec 30, 2010 at 8:17 PM, Steve Smith st...@scsworld.co.uk
wrote:
 I'm not sure I quite understand your question but if you are saying for
example you have two heroku sites setup but they share the same repository
(like staging and live) then you can specify --app as part of the heroku
command line tool.

 Such as:

 $ heroku info --app cloudmailin


 On 30 Dec 2010, at 11:45, femto Zheng wrote:

  Hello, I'm running into a situation,
  while my live site is up and running in heroku,
  some part I need to ask others to modify.
 
  so say,
  I have myapp point to g...@heroku.com:myapp.git,
  then I want to add a new app/repo to use as a collabor repo,
  then say,
  in my local myapp project, I git remote add 
  g...@heroku.com:myapp-pre.git(which
I created),
  then I git push myapp-pre master, then use it as a collabor
repository.
 
  The question is, then the several heroku commands,
  like heroku console, heroku rake etc, how do they know to find
  which repo/app to work with? That's an interesting question,
  and I don't want to two environment mess up together.
 
 
  --
  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 heroku%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 heroku%2bunsubscr...@googlegroups.com.
 For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.




 --
 http://hi.baidu.com/femto
 http://bbs.aisiming.com/

 --
 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 heroku%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 heroku%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 heroku%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 heroku%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.