# UCI NEXTCLOUD DOCKER IMAGE

## Building

## Testing

## Publishing

## Deploying

## Notes

https://www.reddit.com/r/NextCloud/comments/15fhs8n/additional_config_files_seems_to_load_but_then/

Looks like I finally answered my own question after reading this comment

**Any file located in NC\_Installation\_dir/config/ ending with .config.php will be merged and stored as config.php**

from this post

[https://help.nextcloud.com/t/did-you-know-anysetting-config-php/141618](https://help.nextcloud.com/t/did-you-know-anysetting-config-php/141618)

*it seems as if these additional config files are not necessarily read at runtime as the docs seem to indicate rather they get read and merged at some point.*

Well, after goofing around with `occ` I discovered that if one set/delete a dummy key/value all the rest of the configs are then merged into `config.php`.   Further if I want to "update"  I can delete a key using occ, update a key in that additional config file then once again set/delete a dummy key/value and the changes will be merged back into config.php.  With all the values "hardcoded" into `config.php` nextcloud no longer complains about `trusted_domains`.

So this then is my "solution".  After I do `maintenance:install` I just set/delete a dummy key/value and my custom key/values form my additional config files are merged.  Apparently `maintenance:install` does not perform this merging*.*

    occ config:system:set --value true update_config
    occ config:system:delete update_config