It seems that the nix derivation tries to build using a broken version of the purescript nix library it uses (one of the downloads 403s). Would it be possible to get an updated nix derivation?

The tool looks really cool, I'd love to try it out.

Has anyone had any luck getting this to work inside a docker container?
What would I need to map into the container for zfs-snap-diff to see my snapshots?

the ui should provide a feature to recover a file from the backup

if you recover a file from a snapshot, a backup of the actual file are stored under /path/where/the/file/was/.zsd/<FILE_NAME>_<TIMESTAMP>.
which this feature, you can easy recover a wrong overriden file.

This issue is to discuss features of zfs-snap-diff.
Please comment or upvote (:+1:) if you need the feature / downvote (:-1:) if you doesn't.

the ui should provide a 'bookmark' feature for each dataset

if you often need to recover / review a file deep in the directory structure, it could be handy to add a bookmark to this location

This issue is to discuss features of zfs-snap-diff.
Please comment or upvote (:+1:) if you need the feature / downvote (:-1:) if you doesn't.

The zfs-snap-diff link in the top left of the web app goes to a 404 URL: https://j-keck.github.com/zfs-snap-diff

If you try and restore a file from a snapshot that no-longer exists in the dataset you get the error:

Unable to open current file - stat </path/to/file>

zfs-snap-diff should provide the functionality to create zfs snapshots in the ui.

This issue is to discuss features of zfs-snap-diff.
Please comment or upvote (:+1:) if you need the feature / downvote (:-1:) if you doesn't.

Hi,

It seems I failed to notice two things with the original code with #12.
Appologies.

the timestamp given for the record is the snapshot timestamp; is it possible to use the file timestamp instead?
Also; parse-time-string would be happier with a RFC 822 datetime:

"Parse the time in STRING into (SEC MIN HOUR DAY MON YEAR DOW DST TZ).
STRING should be something resembling an RFC 822 (or later) date-time, e.g.,
"Fri, 25 Mar 2016 16:24:56 +0100", but this function is
somewhat liberal in what format it accepts, and will attempt to
return a "likely" value even for somewhat malformed strings.
The values returned are identical to those of `decode-time', but
any unknown values other than DST are returned as nil, and an
unknown DST value is returned as -1."

Currently i rewrite zfs-snap-diff in the dev branch.

Some features are missing (also the documentation), but i think it's better to get some input
before i make a new release.

Maybe someone has some time in the coming days to test the new version and give some feedback.

This would help to get a new stable release.

You can find the binaries here: http://j-keck.github.io/zfs-snap-diff/

Thanks, Jürgen

I think I would love to try this, but it appears to only support HTTP. Please correct me if I am wrong.

This is a concern for me because it would be deployed on production servers.

I´d love to test your work with openzfsonosx.

currently the backup location for files, which are restored from a snapshot is under /path/where/the/file/was/.zsd/<FILE_NAME>_<TIMESTAMP>.
zfs-snap-diff should put the backups under ~/.zsd/....

This issue is to discuss features of zfs-snap-diff.
Please comment or upvote (:+1:) if you need the feature / downvote (:-1:) if you doesn't.

Hi, I am currently working on a pull request (mrBliss/snapshot-timemachine#4) to integrate this tool directly within emacs.

I'm currently using the verbose debug output (-v) to capture the dataset mount path.

An optimal listing would be in to form:

idx | snapshot name | snapshot file | file date

so if currently running zsd -d 15 .spacemacs list outputs

I would benefit from running zfs -d 15 --timemachine .spacemacs list to output

An additional option to omit the headers would be a nice extra.

What do you think?

Just tried this, and it looks broken on Centos7. In the web UI I click on a snapshot under diff and it just gives a spinning wheel endlessly, even when I click elsewhere.

Also there is an option to specify a port other than 12345 but if I try to specify a specific interface like -p 172.100.100.101:12345 ,it doesn't work. I don't want to launch this on all interfaces (-a), this is very insecure.

zfs-snap-diff should automatic create / destroy zfs snapshots

or this is the job for:

• zfsnap/zfsnap
• bdrewery/zfstools
• zfsonlinux/zfs-auto-snapshot

This issue is to discuss features of zfs-snap-diff.
Please comment or upvote (:+1:) if you need the feature / downvote (:-1:) if you doesn't.