Pritambarhate I will advice you to go with the script that a professional black hat will make yoo understand and he to the matching of Heroku, you just have to contact hackerdanielssmith@gmail.com ,stay safe
A simple DIY Heroku replacement to keep your hosting costs down
31–40 of 76 posts
Re: A simple DIY Heroku replacement to keep your hosting costs down
#32I think that products like this occupy a tricky space. Heroku won't win any contests for price, but we know what they do offer - a simple setup, and you can trust that they have experts behind the scenes working to keep everything up-to-date and secure. That's one extreme.
The other extreme is, I set up my own servers by hand or with a handful of custom scripts. Cheap in price, but time-consuming, and I might miss something. The advantage is that I know how every bit of it works if I need to add a feature or set up something weird.
Either extreme makes sense when used for the right purpose, but I feel like it's harder to find a place for things kind of in the middle like this. It has a bunch of nice, handy features, but how much can I trust the maintenance on it? If some sub-item has a security alert, how quickly will it get updated? Will I have to dig into the guts of this thing to fix it? Will that still be true 3 years from now? If I want to do something weird and custom, how hard is that?
Re: A simple DIY Heroku replacement to keep your hosting costs down
#33Well, Dokku [1] is already a good solution to the heroku cost problem. All the power and convenience of heroku commands with the freedom and low cost of docker deployment. It has lets-encrypt ssl support too! [1] https://github.com/dokku/dokku
I'm using Dokku to serve a bunch of sites and love it, it has made deployments a breeze. I did run into some Docker problems (used too much CPU and couldn't connect to its socket, etc), but I don't think it was Dokku's fault, but Docker's. I want to see if I can use Kubernetes as a Dokku replacement (hopefully a more stable one), but I don't think Kubernetes has all the niceties Dokku has (automatic reverse proxying,…
I haven't used kubernetes yet, but https://traefik.io/ was a great reverse proxy in combination with docker swarm. I imagine it works great with kubernetes, too.
Putting a few labels on the containers you want to expose with your reverse proxy is all you need to do. Traefik continuously monitors docker to react to changes. Traefik handles load balancing and automatic certificate generation with ACME, too
Re: A simple DIY Heroku replacement to keep your hosting costs down
#34Well, Dokku [1] is already a good solution to the heroku cost problem. All the power and convenience of heroku commands with the freedom and low cost of docker deployment. It has lets-encrypt ssl support too! [1] https://github.com/dokku/dokku
I used to love dokku until I had 7-minute deployment times for an average application in production. Has that been fixed? Was around 0.6.0 I think.
Re: A simple DIY Heroku replacement to keep your hosting costs down
#35NodeChef is a Heroku alternative which is cheaper that DIY https://www.nodechef.com/
Just playing with the sliders on the pricing page show I'd pay almost double (~130/m) what I pay now for Heroku (~70/m).
I see you're the cofounder of NodeChef. You need to rethink either your pricing or your market position. Also, it's customary to be upfront about conflicts of interest, by declaring "I am the cofounder of NodeChef". Better than trying to hide it (which comes off as scummy), or expecting people to dig through your comment history, which is just lazy.
Re: A simple DIY Heroku replacement to keep your hosting costs down
#36Well, Dokku [1] is already a good solution to the heroku cost problem. All the power and convenience of heroku commands with the freedom and low cost of docker deployment. It has lets-encrypt ssl support too! [1] https://github.com/dokku/dokku
Shameless self plug: we are also building an alternative[1] that enables you to run tons of services on a single node (and to call them easily from front end projects - with the help of autogenerated type safe clients).
Re: A simple DIY Heroku replacement to keep your hosting costs down
#37This, Dokku, Flynn, that 1000+ line bash/chef/ansible script that the guy who used to do your job before he left are all legitimate solutions for deploying apps (and all better than FTP'ing up whatever the developer happens to have on their laptop). But, I feel like the comparison to Heroku isn't great. Heroku saves you from having to do and worry about significant amounts of (I would argue) extremely important admin…
OTOH, the Heroku people aren't personally managing each instance you create; their work is writing the automation code that turns AWS VMs into these more manageable, higher-level pods.
Maybe Dokku and Flynn aren't there yet, but conceptually, is there a real difference between the two? I don't see it.
Re: A simple DIY Heroku replacement to keep your hosting costs down
#38How does this compare with Flynn ? https://flynn.io/
The first thing that comes to mind is that captainduckduck is free and opensource and the product you linked to is a closed source service you pay ($3,499/month) for.
Re: A simple DIY Heroku replacement to keep your hosting costs down
#39How does this compare with Flynn ? https://flynn.io/
The first thing that comes to mind is that captainduckduck is free and opensource and the product you linked to is a closed source service you pay ($3,499/month) for.
Flynn is also free and open source, the pricing is for their management services -- that's explicitly stated in the first paragraph of their pricing page
Re: A simple DIY Heroku replacement to keep your hosting costs down
#40This, Dokku, Flynn, that 1000+ line bash/chef/ansible script that the guy who used to do your job before he left are all legitimate solutions for deploying apps (and all better than FTP'ing up whatever the developer happens to have on their laptop). But, I feel like the comparison to Heroku isn't great. Heroku saves you from having to do and worry about significant amounts of (I would argue) extremely important admin…
While I agree that a script can't match what Heroku does, in the end Heroku shouldn't be used for anything serious. I love Heroku for it's simplicity. They give you very few levers, making it less likely for you to screw up. When we had a production add we faced following issues with Heroku: 1. Frequent downtimes. Heroku would have a 3-4 hour downtime every 2 months. In some cases, site would be down. In most cases y…
> in the end Heroku shouldn't be used for anything serious.
This is a provably false statement. There are thousands of companies running very serious things on Heroku handling load that would exceed the needs of the majority of audience here. All with near zero effort from a developer perspective.
They've also always been transparent about downtime, retrospectively creating/amending cases if required. The only multi-hour outages in the past 60 days afaict affected the ability to launch new processes & use the API but didn't actually cause downtime for apps that were already running (https://status.heroku.com/). That said, uptime for the past 60 days for the US region is > 4 nines, and EU is 5 nines. Better many ops teams achieve.
I was using rolling deploys (and preboot before that) on Heroku without issue back in 2013. I can't speak to the issues you had, but there were (is) a number of documented caveats to be aware of when using it.
You get all of that simply by doing `heroku create; git push heroku master`. Plus a broad range of automatically provisioned, configured, and fully-managed services you can use with a single click.
There's plenty of valid reasons to not use Heroku, claiming one if them is it's unsuitable for anything serious is disingenuous.