3 ms·
Isn't the whole point of PAAS/IAAS offerings the idea that someone else is responsible for maintaining the underlying platform/infrastructure? Not trying to cu
by modarts 14y ago
Isn't the whole point of PAAS/IAAS offerings the idea that someone else is responsible for maintaining the underlying platform/infrastructure? Not trying to cut down your idea; just trying to get a better understanding of some typical use cases.
- zrail 14y agoYeah, that's absolutely the point of PaaS/IaaS things. The point of Dokuen is to be able to deploy those things in a similar environment that is strictly under your control. My use case, specifically, is that I have one app that has a large amount of personal data in it, and another one that doesn't fit under the terms of use of any of the PaaS providers. They're not going to get any traffic outside of me and a few other people and it's totally fine if they aren't available from time to time. By using Foreman and Mason in my own environment, I get to use the patterns that those tools provide (buildpacks, Procfiles) outside of Heroku.
- jpdoctor 14y ago> The point of Dokuen is to be able to deploy those things in a similar environment that is strictly under your control. I'd add that some of us know how dishonest people work, and would never give control of critical items to third parties (because everyone has their price.) Thanks, and looking forward to trying it out.
- simius_ 14y agoThis type of setup makes total sense when you work for an enterprise company that spends way too much money on it's own inefficient IT department to use something as awesome as Heroku. You can run this and have your own internal app server that has the git push simple deployment.
- rhizome 14y agoSometimes those other people work for the same company as you.
- chaostheory 14y agoYeah when I read "personal Heroku" I was thinking something along this line: https://my.cloudfoundry.com/micro https://my.cloudfoundry.com/micro