Home / user-119105

iwein's questions

Martin Hope
iwein
Asked: 2013-01-04 04:58:34 +0800 CST
  • 2

I've managed to surprise myself with some DNS configuration. This is the actual output of my terminal:

[]$ host www.sepa-converter.nl
www.sepa-converter.nl is an alias for sepa-converter.herokuapp.com.
sepa-converter.herokuapp.com has address 184.73.167.111

[]$ host sepa-converter.herokuapp.com
sepa-converter.herokuapp.com has address 184.72.248.52

The result is that if you browse to www.sepa-converter.nl, you do not get the content served by sepa-converter.herokuapp.com.

I've used sepa-converter.nl as an alias for overopsepa.nl. And I want the mails to keep showing up at my Google Apps account. For that reason I've kept the A and MX records, but just changed the CNAMES to point to another server.

Why doesn't this resolve www.sepa-converter.nl to the right heroku app?

UPDATE: I understand that heroku doesn't return the same IP each time and I understand that that's not a problem. The problem is that the http requests serve content that is coming from a different dyno than the one aliased. If you check www.sepa-converter.nl against sepa-converter.herokuapp.com you'll see a different index.html being served.

domain-name-system
Martin Hope
iwein
Asked: 2012-11-04 01:59:47 +0800 CST
  • 0

My client gave me a key and a secret to manage his EC2 things, but to make one of my AMI's available to run I have to fill in the Account Number. Is it possible to deduce the account number from the key and the secret?

Obviously I also asked the client for this information, but since it's weekend and I'm not fond of waiting I wanted to see if I could figure it out myself. Have you done this before?

amazon-ec2
Martin Hope
iwein
Asked: 2012-04-29 03:17:01 +0800 CST
  • 6

I build MVP's for clients regularly. Often I deploy on Heroku so they can see if the product works and demo it to prospects and investors.

Then I have an application deployed on heroku, and it works like a charm, if not for one little thing. The app takes about 30 seconds to start up and heroku has the annoying habit of killing dyno's if they don't get traffic. My client is using the application for demo purposes now, so the load is extremely low and intermittent.

I'm looking for a solution that is preferably:

  • cost effective
  • can be applied to multiple apps simultaneously

What is the best way to avoid having the first request taking 30 seconds?

keepalive heroku