I've been trying to understand how to setup my heroku app, to work with a domain I've bought.
Reading this article https://devcenter.heroku.com/articles/zerigo_dns#configure-dns-servers - I don't understand what should I do in the "Configure DNS Servers".
What exactly should be done in order to configure the DNS in hover.com?
Thanks.
Those are specific instructions for zerigo. If you want to use hover all you have to do is follow this guide.
I should note that hover doesn't really support naked domains in this way but there are other services that you could rely on for that. I bothered them once about it and they said they were working on it so you may be able to have a naked domain on hover in the future.
Related
I´m new on development and found Heroku easy for deploying my app.
I was happy until I got to problems:
Heroku does not provide an IP adress which I need for a white IP list to access an API. I fixed this with a Heroku add-on proxy called Fixie. That is free if under 500 request per month.
The Heroku free plan sleeps after 30 min of inactivity. My app needs to makes API requests at midnight and this is getting difficult because the app is sleeping.
I was thinking to pay the nearest cheap plan on Heroku which make that the app does not sleep. But then I though why not use another platfrom than Heroku.
Does anyone have some sugestions? Any other platform that give an IP so I don´t worry about crossing the 500 request per month?
I was thinking of AWS Elastic Beanstalk. But as I said I´m new at this.
You can use DigitalOcean: the cheapest plan is 5$ a month and you get a Droplet with its own IP address. The Droplet is always running (no inactivity timeout like Heroku).
The main difference is Heroku provides an abstraction layer on top of the underlying infrastructure (you only deal with the application deployment and management) while DigitalOcean delivers a virtual box (ie Ubuntu), however the documentation is great and you can easily find what you need (ie install Docker, etc..)
Couldn’t agree more.
I have been running many applications on Heroku for years now and have faced the 1st problem that you’ve mentioned multiple times.
I tried using Engine Yard instead of Heroku as far as I can remember I never faced the IP issue that you are referring to. AWS is good, but again it’s not without its limitations because its really hard to use. It’s these shortcomings that drive users crazy, isn't it? All I can say is that when I shifted to Engine Yard the set problems I faced considerably dropped. It appears to be a much more usable platform. Check it out.
Here’s a link to Engine Yard, which I hope will help you.
I've got my Node.JS bot builder chatbot all working in the emulator, but I'm not sure how I can get started in allowing my bot to be chatted to by others through the internet, on a web page.
I've seen this article, but this seems to be if we want to host the both through Azure. Additionally, I'm not sure how I'd link the code I made for the bot with this.
This is for a school project for a local company, so I'm fairly sure (and will ask) that they want this to be free to run on their own servers, instead of paying Microsoft.
Can anyone help me understand how this all works?
If you're using MS Botframework & LUIS, you will have to host your webhook somewhere to make it accessible to public. Now, if you do not want to spend a penny for hosting services, I'd like to suggest you one more bot platform dialogflow.com (api.ai) where they have built-in inline editor (Powered by Cloud Functions for Firebase). You will just have to write your code there & say deploy. You won't be charged unless you're using a standard edition.
Now, second thing, if you do not want to do any of these & still want to make it public, you will have to have your own servers & all & expose your IP. Put that computer in the DMZ of your router. That is what it is for. Or, simply forward the needed ports. But here you will have to manage everything on your own like if a server goes down etc. Hope this helps.
We run a whitelabeled site builder -- think squarespace or shopify (different market, though). We currently host on Heroku, but need to be able to offer customers an IP address so they can easily point their naked domains at our service. Although I want to move to AWS at some point, we're a bit short on resources right now, so I need an interim solution for this.
It seems like I should be able to set up a simple proxy server behind a static IP on Route53 or something that would proxy traffic to our Heroku app. But I've little experience with this sort of thing and don't know A) if this is actually the right way to go about it, B) resources to look at or the right tools to check out, or C) if there are commercial services that would be easier temporarily than running it ourselves.
Thanks in advance for any pointers!
PS - Believe me, I know this is sub-optimal, but there are a number of reasons we definitely have to offer an IP.
You could certainly do this, since a proxy or hand-made LB within EC2 can shuttle traffic off to wherever you need. So HAproxy running on an EC2 instance could pass traffic over to Heroku for you.
However, I see this was posted about 6 months ago and I know Heroku has just reconfigured pricing. So maybe that is encouragement to move into AWS now. My only real worry about your above solution is latency. What if you ran an EC2 instance with Varnish to cache your Heroku app(s) and try to mitigate any sluggishness?
I have my app fully deployed for free at https://blooming-summer-8571.herokuapp.com/ but want to start paying for hosting for my own custom domain. I have also bought a domain name that I want to put my app on. What are the best resources or even google search key words that will help me do this through heroku?
Your best bet is to go through the heroku dev center located at:
https://devcenter.heroku.com/
There are topics from the very basics to more advanced ones. You're looking for the custom domain setup, instructions for which can be found here: https://devcenter.heroku.com/articles/custom-domains
I develop on my machine and use my local IIS to test the site. I was thinking it would be really useful for showing people in the office a prototype or demo if I could just IM them a URL to this instance of the site that would be available on the local network in the office. Then they could browse to it instead of having to get up and come over here. Also it would allow them to test it in their browser as an extra perk.
Has anyone done this kind of thing, how would I configure it?
Yes, if you are just using your local IIS, you should be able to hand our your IP or machine name and others could access it. Give this a try and let us know if you have any errors doing so ... please note you might have to toy around with anonymous access permissions so just keep that in mind coming out of the gate.