The config changes in files_external does not come into effect immediately

[skshetry]

I am not able to reproduce this manually, but when writing acceptance tests, a force-scanned for files had to be done for the config to come into effect.

So, in tests, if you set the filesystem to be never scanned automatically, through:

./occ files_external:option <mount_id> filesystem_check_changes 0

and, if you create a file on the storage, it would be scanned and added to the filecache.

What O think is that, there is some time delay in between for the config to come into effect. Maybe, this is okay for real-world usages, but in tests, I had to force-scan for it to come into effect, through:

./occ files:scan --all

Opening this ticket, just in case it's a bug(but, it might be a bug in my code).

[phil-davis]

Does this files_external:option put its setting into config.php ?
If that is where the setting is stored, then it might just be the delay for the changed config.php to be actually used by PHP.

[ownclouders]

GitMate.io thinks the contributor most likely able to help you is @mmattel.

Possibly related issues are #9143 (Nginx Config Does Not Work), #14482 (Nginx config does not work), #27384 (config/ subdirectory does not need to be writeable), #22114 (apps_paths config option has no effect on assets), and #4104 (user_ldap backgroundworker does not pull config from database).