Re: Small tutorial about Heroku/Github
Thanks Thomas, I just discovered your article too. You illustrate the branching very clearly and I like the peek into the under-the-covers git config to dispel all "magic". I've linked to it from another article I posted covering the basic dev pattern "collaborate on github, deploy to heroku" http://tardate.blogspot.com/2009/08/rails-dev-pattern-collaborate-on-github.html Regards, Paul http://tardate.com On Wed, Jun 3, 2009 at 9:08 AM, Giorgio Clavelli wrote: > Thank you very much Thomas > > Giorgio > > > > > --~--~-~--~~~---~--~~ 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't use CNAME and MX records together
Hi Matthew, Not sure about GoDaddy, but I just discovered a work-around for whois... the order of setting up MX and CNAME is significant;-) So for whois.com: 1. Setup MX records first parasite.com. MX aspmx.l.google.com. (etc - all the 7 MX addresses for google) 2. Then setup CNAME parasite.com. CNAME proxy.heroku.com If I do the reverse, whois refuses to register MX records because of the CNAME conflict. This allows me to achieve what I want: http://parasite.com and us...@parasite.com, but I gather that still leaves the issue of some MTAs have difficulty delivering. Love to know if there's a better way... Regards, Paul http://tardate.com On Mon, Jun 29, 2009 at 10:43 AM, Matthew Williams < matthew.d.willi...@gmail.com> wrote: > > I'm in the same boat with this issue. > > Domain hosted with GoDaddy and unable to appropriately get my MX > records to point to Google Apps for Gmail on my Domain while hosting > my App with Heroku. > > Any progress or confirmed working configurations with GoDaddy? > Alternative (free) solutions? > > On Jun 28, 10:02 pm, Paul Gallagher wrote: > > This issue bit me recently since my dns provider (whois.com) just > started to > > enforce no mixing of CNAME and MX records. > > > > The problem I'm having is that I can't figure out a way around this > where: > > (a) both your web services and mail services are hosted (by separate > > providers), and > > (b) you want to use the same domain name for mail and web. > > > > Specific example is using heroku.com for web hosting and google apps for > > mail. If my domain is "parasite.com". I want people to be able to > gohttp://parasite.comand u...@parasite.com > > > > proxy.heroku.com. A 1.2.3.4 # managed/owned by heroku > > aspmx.l.google.com. A 1.2.3.4 # managed/owned by google > > > > Then it seems all I want/need to do is: > > > > parasite.com. CNAME proxy.heroku.com > > parasite.com. MX aspmx.l.google.com. > > > > However, that's exactly what an increasing number of sources are advising > > against (e.g. > http://blogs.eweek.com/cheap_hack/content/dns/dont_mix_mx_and_cname_r...), > > and what it seems the DNS providers are starting to come down hard on. > > > > So I am at a loss. I think you can get around this by caving on the "same > > domain" requirement e.g.www.parasite.com. CNAME proxy.heroku.com > > parasite.com. MX aspmx.l.google.com. > > > > or > > parasite.com. CNAME proxy.heroku.com > > mail.parasite.com. MX aspmx.l.google.com. > > > > But that is _so_ 90's / tail wagging the dog. And it seems we are doing > this > > all because some bad MTA implementations. > > > > Any advice from the heroku standpoint? How have others solved this / have > I > > got my analysis correct? > > > > Regards, > > Paulhttp://tardate.com(for now;-) > > > > > > > > On Mon, Jun 22, 2009 at 2:28 AM, Jason Eggleston > wrote: > > > > > The way I understand DNS, you do not want to have a CNAME record along > > > with *any* other records for the same name. This includes NS and SOA > > > records which every domain has. > > > > > For example, if you have a CNAME and MX record for your base domain, > > > an MX lookup on your domain would result in an MX lookup for > > > heroku.com. Not good. > > > > > For my domain, I use godaddy to host, point the base at > > > 64.202.189.170, and set up domain redirecting (301) with godaddy to > > > the www name. With this service, the whole url is preserved, and www > > > is appended to the beginning as a 301 redirect, or 302 if you want. > > > > > www is a cname to proxy.heroku.com. Works perfectly. > > > > > If you do it this way even for an existing site, eventually search > > > engines will direct users to the www version of your domain. > > > > > The only way to use the base domain safely with heroku would be if > > > heroku started hosting DNS. Google App Engine has the same issue. > > > > > On May 8, 6:36 pm, Adam Wiggins wrote: > > > > Another fix for this is to alias your domain to point to > > > > proxy.heroku.com instead of heroku.com. i.e.: > > > > > > $ host mydomain.com > > > > mydomain.com is an alias for proxy.heroku.com. > > > > proxy.heroku.com has address 75.101.145.87 > > > > proxy.heroku.com has address 75.101.163.44 > > > > > > Although it reads a little less nicely, this avoids having to tinker > > > > with MX records, so perhaps we'll make this the official way to set > up > > > > custom domains. What do you guys think? > > > > > > Adam > > > --~--~-~--~~~---~--~~ 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: performance expectations for 1 dyno 'blossom'?
Thanks for the suggestions Oren, I'll do some more monitoring. Haven't used newrelic before, but heard good things about it. Seems like a good chance to check it out;-) On Mon, Jun 29, 2009 at 9:39 AM, Oren Teich wrote: > > > is current performance (i.e. the past few days) unusual/ are there issues > > being actively resolved? > > is performance recognised as an issue/ are there plans to do anything > about > > it? > > what have other's experiences been like? (network is a factor for me > since > > I'm based in Singapore, but not when compared to other US-hosted sites) > > > That does sound odd. I've had variable performance at times with > Heroku myself. I know that at one point they upgraded something I was > running on, which had a huge performance bump for me. > > are you using anything like newrelic or scout? That can give you a > good feel for where the performance issue is, and help identify if > it's heroku acting wonky or something else. I've used newrelic myself > (the free version) to get a feel for what's going on. > > You can also submit a ticket at support.heroku.com, and they're > usually pretty good about responding. > Oren > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Can't use CNAME and MX records together
This issue bit me recently since my dns provider (whois.com) just started to enforce no mixing of CNAME and MX records. The problem I'm having is that I can't figure out a way around this where: (a) both your web services and mail services are hosted (by separate providers), and (b) you want to use the same domain name for mail and web. Specific example is using heroku.com for web hosting and google apps for mail. If my domain is "parasite.com". I want people to be able to go http://parasite.com and u...@parasite.com proxy.heroku.com. A 1.2.3.4 # managed/owned by heroku aspmx.l.google.com. A 1.2.3.4 # managed/owned by google Then it seems all I want/need to do is: parasite.com. CNAME proxy.heroku.com parasite.com. MX aspmx.l.google.com. However, that's exactly what an increasing number of sources are advising against (e.g. http://blogs.eweek.com/cheap_hack/content/dns/dont_mix_mx_and_cname_records.html), and what it seems the DNS providers are starting to come down hard on. So I am at a loss. I think you can get around this by caving on the "same domain" requirement e.g. www.parasite.com. CNAME proxy.heroku.com parasite.com. MX aspmx.l.google.com. or parasite.com. CNAME proxy.heroku.com mail.parasite.com. MX aspmx.l.google.com. But that is _so_ 90's / tail wagging the dog. And it seems we are doing this all because some bad MTA implementations. Any advice from the heroku standpoint? How have others solved this / have I got my analysis correct? Regards, Paul http://tardate.com (for now;-) On Mon, Jun 22, 2009 at 2:28 AM, Jason Eggleston wrote: > > The way I understand DNS, you do not want to have a CNAME record along > with *any* other records for the same name. This includes NS and SOA > records which every domain has. > > For example, if you have a CNAME and MX record for your base domain, > an MX lookup on your domain would result in an MX lookup for > heroku.com. Not good. > > For my domain, I use godaddy to host, point the base at > 64.202.189.170, and set up domain redirecting (301) with godaddy to > the www name. With this service, the whole url is preserved, and www > is appended to the beginning as a 301 redirect, or 302 if you want. > > www is a cname to proxy.heroku.com. Works perfectly. > > If you do it this way even for an existing site, eventually search > engines will direct users to the www version of your domain. > > The only way to use the base domain safely with heroku would be if > heroku started hosting DNS. Google App Engine has the same issue. > > On May 8, 6:36 pm, Adam Wiggins wrote: > > Another fix for this is to alias your domain to point to > > proxy.heroku.com instead of heroku.com. i.e.: > > > > $ host mydomain.com > > mydomain.com is an alias for proxy.heroku.com. > > proxy.heroku.com has address 75.101.145.87 > > proxy.heroku.com has address 75.101.163.44 > > > > Although it reads a little less nicely, this avoids having to tinker > > with MX records, so perhaps we'll make this the official way to set up > > custom domains. What do you guys think? > > > > Adam > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
performance expectations for 1 dyno 'blossom'?
I've recently deployed a couple of applications to heroku but have been a little underwhelmed at the performance on 1 dyno/Blossom 1. Unfortunately I don't have numbers, but I have a feeling that performance has been much better in the past. Again, without real numbers yet - I just did a simple test of the same page served from heroku and herokugarden. Herokugarden is ~ 3 times as fast!!?? I believe adding dynos will mainly improve concurrency (not single user/single request performance), so I'm a little concerned now that if this is the best heroku can do with 1 dyno, I might have to go look for another place to host my apps (or go back to herokugarden, which I don't think is the idea!). I don't really want to do that (I've even blogged my enthusiams about heroku a few times; don't want to eat crow) So I'm wondering: - is current performance (i.e. the past few days) unusual/ are there issues being actively resolved? - is performance recognised as an issue/ are there plans to do anything about it? - what have other's experiences been like? (network is a factor for me since I'm based in Singapore, but not when compared to other US-hosted sites) Regards, Paul http://tardate.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 -~--~~~~--~~--~--~---
Re: heroku.com or proxy.heroku.com ?
@ngrandy: Likewise. Last week I setup a domain with CNAME -> heroku.com. No problems adding the custom domain to heroku. Setup another domain yesterday with CNAME -> heroku.com Now I can't add the custom domain to heroku; it complains that it needs CNAME -> proxy.heroku.com It seems like something has changed at heroku. But the documentation still says "CNAME -> heroku.com", and my domains setup that way still work fine. Anyone know if there has there been an official change, or is this a problem that needs to get fixed? Regards, Paul On Fri, May 22, 2009 at 3:57 AM, ngrandy wrote: > > I was recently able to add a new custom domain only by using > proxy.heroku.com. However, the previsouly-created custom domains > pointing to heroku.com still work. > > > On May 21, 4:08 am, Kieran Topping wrote: > > Thank you Carson, > > I am well aware that I haven't added the CNAME record yet. > > I just wanted to check whether I should add an alias for "heroku.com" or > > "proxy.heroku.com". > > Many thanks for clearing up my confusion! > > Kieran > > > > Carson Cole wrote: > > > Set the alias to "heroku.com" in the CNAME record. > > > > > Then, add your app in heroku, which will check if the CNAME record has > > > been entered for your domain. As you found, when it checked, the CNAME > > > record hadn't been added, which is why you got the message. > > > > > On May 21, 6:51 pm, Kieran Topping wrote: > > > > >> Hi, > > > > >> There is slightly conflicting information on heroku.com regarding how > to > > >> set up a custom domain name. > > > > >> http://docs.heroku.com/custom-domains > > > > >> says to add a CNAME alias for "your.custom.domain" -> "heroku.com" > > > > >> However, when I try to then add the custom domain via: > > > > >> https://heroku.com/myapps/MyAppName > > > > >> I get a message saying: > > > > >> Please check that you've configured this domain name with your > provider. > > >> Check the domain at the command line with "host your.custom.domain", > it > > >> should return output like "your.custom.domain is an alias for > > >> proxy.heroku.com" or "your.custom.domain CNAME proxy.heroku.com". > > > > >> i.e. it states "proxy.heroku.com" rather than "heroku.com". > > > > >> Does anyone know which is correct? > > > > >> (NB it's slightly tricky for me to just "try both and see which works" > > >> as I have to go through [two!] third parties in order to add the CNAME > > >> alias!) > > > > >> Thanks in advance, > > > > >> Kieran > > > --~--~-~--~~~---~--~~ 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: www in domain
Hi Morten, please +1 that request! I had a similar requirement coming up, and was going to ask the same question. But in my case it is specifically to support "multi-teneted" applications. If you look around, you can find quite a few examples of this in the wild. e.g. if I am running a site called: abc.heroku.com .. but wish each member/company registered on my site to have their own space in the domain name I would want: companyx.abc.heroku.com companyy.abc.heroku.com .. instead of something more conventional like: abc.heroku.com/companies/companyx abc.heroku.com/companies/companyy The difference is really one of branding, but may be really significant if I am trying to lure corporate clients. NB: I assume the same problem applies even if the heroku app has been blessed and has its own domain name? i.e. abc.com - ok companyx.abc.com - not ok companyx.abc.com - not ok Regards, Paul On Thu, Jul 17, 2008 at 1:25 PM, Morten Bagai <[EMAIL PROTECTED]> wrote: > > Hmm... I don't think we ever anticipated anybody wanting/needing > that. It doesn't seem like a conventional way of using subdomains to > me. I'll make note of it as a feature request for now. > > Best, > > /Morten > > On Jul 16, 2008, at 8:58 PM, Abolfazl wrote: > > > > > yes it's correct. that is my question. > > why don't that work? > > > > On Jul 15, 1:04 am, Morten Bagai <[EMAIL PROTECTED]> wrote: > >> Do you meanwww.yourappname.heroku.com?That won't work - I don't > >> think we were anticipating anyone would actually want to use that > >> format. I want to make sure I understand your question right, so > >> please let me know if this answers it. > >> > >> /Morten > >> > >> On Jul 11, 2008, at 11:09 PM, Abolfazl wrote: > >> > >> > >> > >>> when i add www in domain name in my browser my web app is not > >>> opened. > > > > > > > > --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: App names cannot start with numbers - incorrect validation?
cool, thanks Adam On Thu, May 22, 2008 at 3:21 AM, Adam Wiggins <[EMAIL PROTECTED]> wrote: > > I agree that app names should be able to start with numbers, so I've > made the change. It'll be available in the next deploy, probably > today or tomorrow. > > Adam > > > > --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
