depends on #4

Crashes even though target is set in the profile and given as a cli argument.

punktf -v --source . deploy $PROFILE --target . --dry-run
[2021-08-20T17:12:19Z DEBUG punktf] Parsed Opts:
    Opts {
        shared: Shared {
            source: SourcePath(
                ".",
            ),
            verbose: 1,
        },
        command: Deploy(
            Deploy {
                profile: "linux_arch_archx",
                target: Some(
                    ".",
                ),
                dry_run: true,
            },
        ),
    }
The application panicked (crashed).
Message:  No environment variable `PUNKTF_TARGET` set. Either set this variable, use the `-t/--target`
				argument or use the profile attribute `target`.

Look over all log's and check if the level is appropriate

Resolve stuff like ~ and maybe environment variables like $HOME when evaluating the profile and dotfile target.

There should be a issue template in place before we release v1.0 so if users want to report issues it is done in a streamlined way.

Maybe punktf should inject some general system variables for templates to use. These will only be accessible by the current process:

• PUNKTF_OS: OS running the punktf process, like windows, unix, ...
• PUNKTF_TARGET: Target directory for the profile
• PUNKTF_SOURCE: Source directory for punktf

it would be nice if one could print to the console using an instruction that does nothing else (similar to comment).

Before starting the deployment, group all items by priority. Then deploy in sorted order (highest first). This allows for specilization of single items (when used together with generic directory deploy) and can reduce disk read/writes.

Look roughly through every method and check if there is something to clean up or improve

So that some secrets or all dotfiles can be encrytped

Export all files relevant for a profile to be able to share it with other people:

• Profile itself
• All items required by the profile
• Collect needed ENVIRNOMENT variables???

Use this for diagnostic reporting: https://github.com/brendanzab/codespan

Similar to https://github.com/sharkdp/fd/blob/master/src/exec/job.rs

Adds file to the source/dotfiles directory and also appends an dotfile entry in the profile file.

• Action which tests installation
• Action which tests simple deployment with all cases/options covered

take file as input change it and return it (e.g. replace CRLF => LF)

• Ability to extend more than one
• Be able to blame (save from which profile option/setting came from)

Update README to current state before 1.0 Release.

Also Add:

• Explaination of PUNKTF_SOURCE/TARGET
• Setup Instructions
• Better Profile example?

When running punktf -V it only prints punktf and no version detail

Add a cli option (e.g. --output-json) to export the created Deployment to a file/stream

This will prevent some write operations as well as skip some unnecessary user merge ask function calls.

Add at least one line of documentation to each method and file

Check if typical user errors produce readable error messages and not undefined behaviour

Set the following description:
⚡ A cross-platform multi-target dotfiles manager

Add the following tags:
rust, dotfiles, cli, dotfile, dotfile-manager

Have a list of symlinks in the profile that are created during deployment.

In my case, I want to automatically create symlinks in my home folder that link to other files on my system like .ssh config from windows mount to WSL.

Implement --quiet, which only logs errors

punktf deploy custom-wsl-debian is lengthy to type.
One should be able to set aliase for profiles:

aliases:
- deb
- debian

so I can simply do punktf deploy deb

Add a --target cli argument similar to --source.

Checks for:

• Item required by a profile but is missing
• Invalid templates
• Items which are not referenced anywhere (no profile requires them)

Example

Take the error from either serde_json or serde_yaml and extract more information. Also put a prefix of profile failed to parse infront.