#tool #filesystem #file #cli

app file-map

Utility to map files into directories according to rules

2 releases

0.1.1 Sep 12, 2018
0.1.0 Sep 12, 2018

#38 in #tool

Download history 11/week @ 2018-09-12

3 downloads per month

MIT license

49KB
1K SLoC

Map

Build Status Build status Version info

A utility to map files into directories according to rules.

I created this to make it easier to organize similarly-named files into the same directory with human-friendly names. Specifically, this made it easier to organize all the book files from Humble Bundles after downloading them flat into my Downloads directory1.

Usage

Clone this repository, then build using cargo build --release using the stable toolchain.

Options

  • -n, --dry-run - If set, files and/or directories will not be created or deleted. This is useful to run with at least one level of verbosity to verify if this tool is doing what you expect.
  • -v[vv] - Sets the level of verbosity. One v will output enough information to see when a file or directory will be created. Higher levels give you more information about rules and files being matched.
  • -r, --rules - Specifies the file to be read for rules, which have a format of a single rule per line. See examples for what those look like. Exclusively specify this argument or a single rule as the first positional argument.
  • -s, --source-dir - Specifies the directory to read for files to perform mappings on. Both currently supported rules do not recurse and only operate on regular files (i.e. not directories or symlinks).
  • -d, --dest-dir - Specifies the directory to perform mappings into. For example, the relative destination specified in a Copy mapping is relative to this directory.

Rules

Two rules are currently supported, for copying and moving files:

  • Copy
    • Format: c /<Regex>/ <Relative destination>
    • Spaces before/after the c do not matter
    • Whitespace before/after the first non-whitespace characters of <Relative destination> are stripped
    • <Relative destination> may have multiple path components, all intermediate directories will be created
    • <Regex> is run against the file name (including extension) of each file in source-dir, not its entire path
    • Files that match the <Regex> are copied into <dest-dir>/<Relative destination>/<Matched file name>, preserving the original file
  • Move
    • Format: m /<Regex>/ <Relative destination>
    • Spaces before/after the m do not matter
    • Whitespace before/after the first non-whitespace characters of <Relative destination> are stripped
    • <Relative destination> may have multiple path components, all intermediate directories will be created
    • <Regex> is run against the file name (including extension) of each file in source-dir, not its entire path
    • Files that match the <Regex> are moved into <dest-dir>/<Relative destination>/<Matched file name>, deleting the original file

Examples

Dry-run a single rule to test moving files with lime in their name in test-source to test-destination/Lime Files:

map -s ./test-source -d ./test-destination -v -n 'm/lime/Lime Files'

Execute rules from a file rules.map on files in test-source with destination test-destination:

map -s ./test-source -d ./test-destination -r ./rules.map

Fot the last command above, if rules.map included the following content:

c/lime/Lime Files
m/orange/Orange Files
c/apple/Apple Files

And the file structure looked like this to start:

├───test-destination
└───test-source
        lemon.txt
        lime.txt
        orange.txt

After running the command, it will look like this:

├───test-destination
│   ├───Lime Files
│   │       lime.txt
│   │
│   └───Orange Files
│           orange.txt
│
└───test-source
        lemon.txt
        lime.txt

Errors

This tool attempts to catch errors before performing any filesystem modifications and for those that it doesn't it stops as soon as any errors are encountered. This tool first parses all the rules, determines what actions to perform (e.g. file moves and copies), then performs those actions. If there's a problem parsing the rules (e.g. invalid regex in a Copy rule) or determining the actions (e.g. the source directory cannot be read) then no filesystem modifications occur and a helpful (hopefully) error message is displayed.

If this tool encounters an error when performing actions (e.g. the destination directory is not writeable), then the tool stops performing actions immediately. It does not attempt to roll-back modifications that have already been made, so as always be careful with destructive filesystem actions like moving files with a Move action.

1: It looks like that gist has since been improved to allow downloading into nicely-named folders.

Dependencies

~3MB
~57K SLoC