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

Support folder exclude via .noimage file filter #1084

Closed
mrtumnus opened this issue Mar 22, 2024 · 3 comments
Closed

Support folder exclude via .noimage file filter #1084

mrtumnus opened this issue Mar 22, 2024 · 3 comments
Labels
feature New feature or request wontfix This will not be worked on

Comments

@mrtumnus
Copy link

Is your feature request related to a problem? Please describe.
I already have .noimage hidden files to exclude folders throughout my Nextcloud file tree. I would prefer not to have to add additional .nomedia or .nomemories files.

Describe the solution you'd like
Add .noimage to the existing support for .nomedia and .nomemories file exclusion filters.

Describe alternatives you've considered
I could go through and make copies all of my .noimage files and rename them as .nomemories/.nomedia.

Additional context
The .noimage (and .nomedia) filters are already supported in the Recognize and Photos apps. See:
nextcloud/recognize#457
nextcloud/photos#944

@pulsejet
Copy link
Owner

I could go through and make copies all of my .noimage files and rename them as .nomemories/.nomedia.

Please do this. This is getting out of hand; each of these exclusions imposes a performance penalty.

.nomedia is the standard; I don't know why Nextcloud decided to randomly come up with .noimage. The implications are also unclear; are videos not excluded? It's not obvious.

@pulsejet pulsejet closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2024
@pulsejet pulsejet added the wontfix This will not be worked on label Mar 22, 2024
@pulsejet
Copy link
Owner

pulsejet commented Mar 22, 2024

I could go through and make copies all of my .noimage files and rename them as .nomemories/.nomedia.

Just wanted to point out this is a one-liner

find <path-to-nextcloud-data> -type f -name '.noimage' -execdir mv {} .nomedia \;

Then you'll probably want to rescan

occ files:scan --all

@mrtumnus
Copy link
Author

Please do this. This is getting out of hand; each of these exclusions imposes a performance penalty.

.nomedia is the standard; I don't know why Nextcloud decided to randomly come up with .noimage. The implications are also unclear; are videos not excluded? It's not obvious.

Fair enough! For some reason, I recall having to figure out whether to put .noimage vs .nomedia based on which applications I wanted to be able to find content. So, for a music/video folder, I would put the .noimage file. But for documents/software folders, I'd put .nomedia. But I don't remember that use case specifically. I'll go with .nomedia as the standard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request wontfix This will not be worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants