3 ms·
one variable is the thing after @, IIRC called "instance" but you can use that variable to specify EnvironmentFile that has more variables :) and it also neat
by ilyt 3y ago
one variable is the thing after @, IIRC called "instance"
but you can use that variable to specify EnvironmentFile that has more variables :)
and it also neatly get per-instance config into separate file
or use configuration management to generate per-service files instead of using instances
- yjftsjthsd-h 3y ago> but you can use that variable to specify EnvironmentFile that has more variables :) I mean, you could, but when you really only had 2 variables that feels pretty kludgy. > or use configuration management to generate per-service files instead of using instances I suspect that's what I actually did, since ansible/chef/puppet/whatever is happy to nest for loops and template the result. It was just annoying that I couldn't do it in place.
- ilyt 3y agowell, instances weren't really done to customize variables, their design was pretty much to do "a program that can be given a different config file as a parameter", like it is done for say postgresql instances.