Yeah, 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.
> 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.)
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.