Ive been trying to use OwnCloud on several occasions, however I keep running into issue syncing files. For example it cannot upload .htaccess file or .cs. Is there anyway I can remove all restrictions on file types? I keep finding a way to allow one certain file types and then find another exception.
The biggest issue I found is when I reset my PC I realised it hadnt synced a load of files and so had to restore from a backup.
Any ideas how to allow all types of files?
tflidd
June 27, 2017, 10:02pm
2
.htaccess is hardcoded because you can mess up your webserver configuration:
opened 10:10PM - 23 Feb 16 UTC
closed 01:37PM - 18 Dec 17 UTC
enhancement
comp:filesystem
Hi there,
We have been looking to deploy OwnCloud on our company servers, as a … replacement for our existing sync provider, as we don't like the idea of our data being held on third-party servers.
However, there is currently one thing that is blocking us, which is that the default sync settings in the OwnCloud client do not meet the basic sync requirements of file synchronisation, namely there are important files that are excluded from the sync. The specific files that affect us (as a web agency) are .htaccess files, and hidden files in general (though there may be others, as I haven't done an exhaustive check of the list yet).
We have removed .htaccess files from the block list on the server, but it appears that the client is still blocking them.
I am aware that there are settings in the client (or rather, somewhere on the client machine, as you can't remove the .htaccess file exclusion from within the GUI). However, this means that we are dependent on all employees correctly setting these settings on every machine/installation that they use, and hoping they don't get modified when the client is upgraded (as I have read reports of on the forums).
Sync software that doesn't sync everything is, frankly, pointless - in fact, it's downright dangerous if users aren't aware of the exclusions. As a company, we need to be certain that everything we expect to be synced _is_ being synced, always, and not be reliant on individual employees to enforce this.
So enough of the complaining - let's make a constructive suggestion to try and resolve this issue, and turn OwnCloud into a fully enterprise-ready product.
What I would like to see is the ability for the exclusions to be controlled by the server admin, so they can just be set in one place, so the software 'just works', straight out of the box (like most other sync services).
The way I would manage it is by adding a `client_config.php` file in the config folder, which can be used to set the default client configuration. (The settings could go in `config.php` but it makes sense for me to separate out the server and client configuration settings.).
Only sync-related settings would be configurable from the server, specifically we would need a `sync_hidden_files` boolean setting, and an array of `ignore_patterns`. This latter setting would need to handle the 'can be deleted' flag, so would either be multi-dimensional (with each entry containing two properties, `pattern` and `can_be_deleted`) or be split into two arrays, one for each type of exclusion.
It should also provide a way to specify whether the client should allow the user to over-ride these settings (probably on a per-ignore-pattern level).
When the client initiates the sync, it will pull down the server config and then apply whatever additional local config has been specified (respecting the 'can change' settings).
PS - I am well aware of why syncing .htaccess file _could_ be dangerous if you haven't configured your server properly, and that is not relevant to this issue. This issue is about providing appropriate software configuration to support people who are able to secure a server properly and who want their sync software to, well, sync.