Yet when I visit my account (signed up a while ago) it's forcing me to a credit card page regardless of which option I choose?
Show HN: Build your own Heroku on your own servers
91–100 of 110 posts
Re: Show HN: Build your own Heroku on your own servers
#92At $9/month I suspect you are drastically under-valuing the service you provide. Sysadmin time is expensive, and your value proposition is the same as Heroku: pay us so you don't waste time sysadmining your boxes. Time is unimaginably precious for small SaaS shops, and if you deliver what you promise, it's worth far more than $9/month. Not to nay-say, but if you don't price according to value delivered, you don't sta…
Actually no I think $9/month is appropriate. A heroku dyno is about $35 a month, and you have a full on solid highly supported service. Here you pay $9/month + server fees which say with the micro instances comes out to about $14 bucks a month. So by doing it on my own EC2 with this service a small instance comes out to about $24. Only thing is though, here you have the option of choosing a larger instance type and b…
Re: Show HN: Build your own Heroku on your own servers
#93Why does the FAQ say "Yes! You can deploy to one server for free forever" Yet when I visit my account (signed up a while ago) it's forcing me to a credit card page regardless of which option I choose?
Re: Show HN: Build your own Heroku on your own servers
#94Nice. As a provider of unsupported hardware, I'd be interested in some "how to make it easy for us to support users on your hardware" page. I really do think that there is a place in the market for something like this, and the more providers you support, the better off both you and your customers are.
Re: Show HN: Build your own Heroku on your own servers
#95Does it come with its own random load balancing, too? Sorry, couldn't help it ;)
Re: Show HN: Build your own Heroku on your own servers
#96Earlier quoted context omitted.
Yep! Digital Ocean just released the bit of their API we needed - so yes they'll be supported soon!
I will also plan to move some client apps to this if you support digital ocean. Would love notification on that.
Re: Show HN: Build your own Heroku on your own servers
#97Earlier quoted context omitted.
Thanks for the question - there is a little more detail here: https://www.cloud66.com/help/cloud66_stack Happy to answer specific questions
How does the nginx fit in? Do you install an instance of nginx onto every single box? Or can you elect to use a web server box as your frontend nginx and proxy request back to a set of separate servers running instances of passenger?
Re: Show HN: Build your own Heroku on your own servers
#98Heroku and the like are fine for prototyping and small apps, but when you start developing complicated and/or popular apps, at some point you are paying a service tons of money to avoid optimizing at the systems level.
I'm a "devops" sysadmin and sitting with my developer every day makes us both so much more effective. "Hey sysadmin, if 1000 requests to this module in my app happen it breaks, can we figure out why it crashes the server?". To which I reply, "yes developer, after we ran some tests, it looks like your code is so efficient and effective, that there aren't enough available tcp/udp ports to support the number of requests it is able to handle. I can increase them on your default AMI if you like. It will result in a 3000% increase in the number of active users we can sustain on a given instance".
The no-ops position is: Let's just pay for more servers. The DevOps position is: Let's optimize.
The difference may seem small, but if you are paying $20k a MONTH for your Heroku bills, not to mention supporting 3k servers for your app on AWS (or insert provider x), do you still think hiring a $100k/year sysadmin is such a bad decision?
The devs can still develop a method to quickly deploy code... or just use Asgard, and avoid all of the chaos that can happen if something goes wrong. The sysadmins understand your code and how it is interacting with the server. You don't end up paying tons of money to support a very basic application that has simply never been optimized.
Sysadmins in a devops world do not usually have any control over when builds can be pushed - they assist with optimizing. So if something breaks, the blame falls on devs, not ops.
Unoptimized app (rapgenius example): $20k/mo = $240k/year Sysadmin: ~$100k+/year and a minor (given devops mentality) increase in deploy time = priceless
Not all cases are the same, but the start-up mentality doesn't usually work at scale.
Re: Show HN: Build your own Heroku on your own servers
#99Having a platform to simply deploy code is great, but there seems to be a lot of hate for sysadmins over the past few years. Heroku and the like are fine for prototyping and small apps, but when you start developing complicated and/or popular apps, at some point you are paying a service tons of money to avoid optimizing at the systems level. I'm a "devops" sysadmin and sitting with my developer every day makes us bot…
Re: Show HN: Build your own Heroku on your own servers
#100Having a platform to simply deploy code is great, but there seems to be a lot of hate for sysadmins over the past few years. Heroku and the like are fine for prototyping and small apps, but when you start developing complicated and/or popular apps, at some point you are paying a service tons of money to avoid optimizing at the systems level. I'm a "devops" sysadmin and sitting with my developer every day makes us bot…
Where do you find sysadmins for high availability systems willing to work for $100K per year?