3 ms·
What I imagine is something like the Procfile for Heroku. The app decides what it runs and how, you can set configuration like domain, whether the application
by avitzurel 10y ago
What I imagine is something like the Procfile for Heroku.
The app decides what it runs and how, you can set configuration like domain, whether the application is public/private etc...
Once you push the application to the scheduler it will handle the rest.
- kozikow 10y agoAh. Quite a lot of things you mention are possible by dynamically generating yaml config. I wrote a blog post about using go kubernetes library to generate yaml : https://kozikow.com/2016/09/02/using-go-to-autogenerate-kubernetes-configs/ https://kozikow.com/2016/09/02/using-go-to-autogenerate-kube.... It's quite nice, even for static config IMO, due to type safety. You can easily write golang binary that would ask user series of questions "what database would you like", "do you want public access", etc. and get yaml as output.
- avitzurel 10y agoYup. What I am saying is this: This should be a part of the core offering IMHO. I think most people choose Heroku over rolling their own infrastructure simply because of the ease-of-use for getting started.
- ecnahc515 10y agoThat's basically what Deis does. They use Kubernetes as the backbone and build a heroku layer on top.