heartsucker
heartsucker
There's a lot of path names that illegal because of FAT/ Windows compatibility. Someone might not like this since they are only deploying to *nix. Some of the checks could...
Because no one is going to try to download `u64::MAX` sized targets.
Even just to keep myself organized. Off the top of my head, it should include things like what to log and at what level to log it.
This would allow the director and image repo roles to share a place to store images while they keep their metadata separate.
Also, only should be run and post on the stable branch. All 3 is overkill.
A disadvantage of JSON is that in order to verify the metadata, it has to be parsed first. It would be better to use a binary protocol that lets us...
Currently the plan is to only use `sha256` and `sha512`. Note: `sha1` and `md5` are out of the questions. If someone wants to tackle this, don't implement those.