Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore files on server side #9542

Closed
kurtgeebelen opened this issue Jul 9, 2014 · 14 comments
Closed

Ignore files on server side #9542

kurtgeebelen opened this issue Jul 9, 2014 · 14 comments

Comments

@kurtgeebelen
Copy link

Hi all,

I have some folders that I have on my ownCloud via SMB. Scattered throughout these folders are subfolders that are needed on the server (all called .metadata), but that I don't want to sync to other machines, or even show up in the web client.

I have found that for the reversed problem where a client creates those type of files that you don't want to sync, you can put it in sync-exclude.lst, but not something the other way around.

Would this in any way be possible? E.g. a similar sync-exclude.lst that the admin can fill in, such that those files are ignored on the server side?

@RuudschMaHinda
Copy link

I second that idea, since it is exactly what I need in a heterogenous environment where every Mac creates a ._* and .DS_Store* which has the Windows-Users all confused and sometimes opening the wrong documents.
This would make my job a lot easier if I could just implement ignoring these kind of files on the server side.

@gsosna
Copy link

gsosna commented Oct 24, 2014

+1
Using foldersync on Android it creates temporary file for the duration of upload with extension .tacitpart.~3eb5
It'd be awesome if I could prevent the server from synching the files to the clients.

@DeepDiver1975 DeepDiver1975 modified the milestone: backlog Mar 21, 2015
@justmiles
Copy link

Adding my +1
I'm surprised there hasn't been more demand for this. Is there a workaround?

@ghost
Copy link

ghost commented Feb 8, 2016

Just to have a context why this was closed:

A new app is now providing this functionality: https://apps.owncloud.com/content/show.php/files_filter?content=174667

@fduraibi
Copy link

@RealRancor The app doesn't solve the problem the OP is talking about. I have never needed to exclude by file type, I always exclude by file/ext names like *.tmp .git *-debug ....etc just like sync-exclude.lst but I want that at the server level. My server is full of these files that were synced by clients that are missing the exclude rules or where synced before I added the rule.

I would love to have a server exclude list that will update the clients and also delete previously synced files/folders that matched the exclude list.

@ghost
Copy link

ghost commented Mar 17, 2016

@fduraibi
Copy link

@RealRancor That is just a request from a user and it is not implemented. The way that filter works is different from what we are asking for. The app deletes the files from the server after getting synced. I don't want the file to be synced to begin with.

Just like how you can add patterns to the client "Ignored files" there should be an option to allow the user to sync that list (or some of it, like a check box for each element) to the server to be populated to the other clients for the same user.

@ghost
Copy link

ghost commented Mar 17, 2016

If you think this is something which should be included in core just create a new feature request specifying your requirements. It seems you have currently different requirements as the OP. Maybe some one will pick it up

@ghost
Copy link

ghost commented Mar 17, 2016

Maybe one of those still open feature requests are already matching your requirements:

#19385, #22607

@RuudschMaHinda
Copy link

@fduraibi just add this to your config.php of your owncloud server installation
you can add any more number of files like this. I just chose those nasty tmp files from the mac users

'blacklisted_files' =>
  array (
    0 => '._*',
    1 => '.DS_Store',
    2 => '.DS_STORE',
    3 => '.ds_store',
  ),

et voilà, those files and all files starting with ._ never even get uploaded.
this information is readily available in the documentation, just as it says in the reason for what this was closed for.

@bonanza123
Copy link

@RuudschMaHinda I added

  'blacklisted_files' =>
  array (
    0 => '._*',
    1 => '.DS_Store',
    2 => '.DS_STORE',
    3 => '.ds_store',
    4 => '.log',
    5 => '.bbl',
    6 => '.out',
    7 => '.blg',
    8 => '.aux',
  ),

to my /var/www/owncloud/config/config.php. Deleted some .log files via webinterface and then added some via the owncloud client and they are still being uploaded. Am I doing something wrong?

@RuudschMaHinda
Copy link

Yes, you are doing something wrong:
you exclude files that are solely named .log that means any file that is named abc.log will get uploaded. if you want all files ending in .log not be uploaded you should name it *.log
(see filename character placeholders)
so in your case, you want to do this:

  'blacklisted_files' =>
  array (
    0 => '._*',
    1 => '.DS_Store',
    2 => '.DS_STORE',
    3 => '.ds_store',
    4 => '*.log',
    5 => '*.bbl',
    6 => '*.out',
    7 => '*.blg',
    8 => '*.aux',
  ),

there is no ' * ' before the .ds_store files, because that is their actual filename in my example and the '._*' stop any file that starts with '._abc' to not get uploaded, again the asterisk meaning 'whatever comes here is valid'
I hope I could help

@kiu-ball
Copy link

@RuudschMaHinda

This does not work. Looks like wildcards are not supported at this point.

@lock
Copy link

lock bot commented Aug 4, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants