Allow user to add to ignore_files list

[k3vmcd]

Allow the user to append filenames to the ignore_files list.

phockup/src/phockup.py

Line 13 in 4bac6db

ignored_files = (".DS_Store", "Thumbs.db")

Should allow the use of a flag, such as -i, to accept both:

1. Multiple filenames within the command line (as in -i filename1.txt file2.docx or -i filename1.txt -i file2.docx)
2. Text file with exclusion list on multiple lines (as in -i /path/to/phockupIgnoreList.txt with contents of phockupIgnoreList.txt being:

   filename1.txt
   file2.docx

(The flag may need to differ for these two, such as using -i for in-line filename exclusions and -n for passing an ignore file).

This ignore feature should allow extension-level exclusions, such as *.txt as well as folder level exclusions (particularly for hidden folders), such as ./.hidden/

[k3vmcd]

Example folders/files to allow user to exclude:

./.stfolder
./.stignore
./Camera/.inflight
./Camera/.inflight_lowres
./.tmp.drivedownload/
./.owncloudsync.log*
./.sync/
./.csync_journal.db
.Spotlight-V100
.Trashes
~*
ehthumbs.db
desktop.ini
._*
.thumbnails

[ivandokov]

This is a great idea. If you can come up with a PR it will be awesome.

[scubachristopher]

What would make this really powerful is to invert this enhancement to indicate what files you want to INCLUDE. The reason is there are directories that contain SOME images / movies you want, but you don't want to disturb the rest of the content. Listing what you want excluded will mean iterating on file types you don't want, running the script, seeing it took file types you didn't know were there, repeat.

I propose including extensions that would be processed, and perhaps an option that says it will look for exif data in EVERY file, and if it finds it (regardless of extension), it will process it. Or "include all photo and video media" and your app maintains a config of extensions that encompasses.

Don't know Python else I'd help.

Love the work -- thank you so much.

[unapproachable]

I'm working on this and want to make sure no one has any opposition to leveraging YAML for the configuration file. My intention is to introduce phockup.yaml for this specific feature, but as a general concept for the app. It will be easier to (eventually) added directory and inclusion support in a well-formed(-ish) YAML structure than introducing a collection of configuration files specified on the command line.

I also intend on allowing an alternate configuration file to be specified so we can go with phockup.yaml for a default config and then allowing for an override configuration file for specific runs (e.g. phockup-video.yaml). I also intend for the app to run as it does today if no file exists or is specified on the command line.

Input/opinions welcome before I get too far down this path. Or thumbs up emojis is fine too.

[ivandokov]

I don't mind having yaml config file. My only suggestion is to use yml file extension or have the option to use both.
I don't see any point in supporting more formats so yaml is fine.