pvgoran
pvgoran
I'm not a fan of dereferencing symlinks either, but I think it's worth mentioning that you can create an endless loop situation even without it. It can be set up...
While this kind of warnings can be quite useful in certain situations, I doubt they should be enabled by default. Both types of symlinks (out of backed-up data, and absolute)...
> Add an option to restic to include the targets of symlinks into the backup. Do you mean adding both the symlinks and their targets?
How would the symlinked files/directories be represented in the snapshot, then? What if the `restic backup` command line has just directory A which has multiple symlinks whose targets are all...
IMHO "rewrite" conveys the meaning the best.
I expect performance to be worse, and in some cases, much worse, when using `restic mount`. (I remember there were reports on very long delays just to list the directory...
As far as I see this is not completed. However, on the table in https://http4s.org/v0.23/docs/integrations.html "Ember" is said to have "Websocket Client". Is this an error in the documentation?
I think the only reason to enable interaction with the page contents (and is a part of the frame contents) is to set `backgroundactive` to `false`. But it will change...
I made a mistake, it should be `backgroundactive: true` instead of `backgroundactive: false`.
I agree, it would be probably better to remove the auto-generated Operation IDs altogether. The best code is no code at all!