4 ms·
What you're saying is exactly what I said in the first paragraph. Containers discover the config and configure themselves. But where do those containers come fr
by FooBarWidget 13y ago
What you're saying is exactly what I said in the first paragraph. Containers discover the config and configure themselves. But where do those containers come from in the first place and how to you build them? Where does that container, containing your in-house app, come from? That is where Chef/Puppet may come in.
- justinsb 13y agoI was thinking that there would be a generic Rails container (like a Heroku buildpack), that reads the location of your Rails code from the configuration, downloads it, and runs it. So, just like Heroku buildpacks, you can create your own, and you can even create one with your app baked in; but most people would end up using an off-the-shelf container. But this is just my interpretation! Your approach may be better, and it doesn't look like CoreOS will care which way you want to do things!