4 ms·
> not to ever have a talk about user IDs, using a sane config .d layout on RHEL, etc. again until you have to maintain/debug/etc N^N combinations/branches of c
by cat199 9y ago
> not to ever have a talk about user IDs, using a sane config .d layout on RHEL, etc. again
until you have to maintain/debug/etc N^N combinations/branches of common code used within the different self produced containers to accommodate all of this 'freedom'...
- acdha 9y agoCould you explain the scenario you have in mind? If you're having trouble maintaining convention across teams producing different shared components, that seems likely to cause problems no matter how you end up deploying things. (This is similar to the argument for containers with developers who aren't great sysadmins: they're usually making changes anyway and this way they don't have root on the host, etc.)