3 ms·
> you're having people modify files that you will also change How is this different from the ever changing nginx configuration files? I think the underlying p
by smokel 3y ago
> you're having people modify files that you will also change
How is this different from the ever changing nginx configuration files?
I think the underlying problem is that various programs use different ways of shipping things. Some include configuration in source code, others require one to read a book to setup a configuration file, others have a database with configuration settings.
If it weren't for us humans creating these things, we would probably have settled on a single interface.
- citrin_ru 3y ago> How is this different from the ever changing nginx configuration files? Nginx developers don’t change configuration files, they only provide an example config - you can create your own config based on this example but you don’t need to update it if an example will be changed in a later release. Package maintainers in many Linux distributions is another story - they usually want to own nginx.conf and end user only drop files into sites-available/enabled and conf.d. I don’t like this approach but it provides easier start.
- jraph 3y agoOn the other end, I've yet to find apt complain that the nginx.conf file from the package was updated, so I guess this is reasonably well handled.