Currently when two different articles reference the same image.png or other file, both these articles get a copy of that file in their output directory. This is wasteful. We want to dedup this eventually.
There's a few ways this could work:
If an article references an already existing file we instead add a symlink to it
all files get put in some directory like /files/sha2hash.extension, all articles then symlink to that file with the desired filename.
The first option probably makes sense? I'd need to investigate how this influences caching too.
Currently when two different articles reference the same image.png or other file, both these articles get a copy of that file in their output directory. This is wasteful. We want to dedup this eventually.
There's a few ways this could work:
- If an article references an already existing file we instead add a symlink to it
- all files get put in some directory like `/files/sha2hash.extension`, all articles then symlink to that file with the desired filename.
The first option probably makes sense? I'd need to investigate how this influences caching too.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently when two different articles reference the same image.png or other file, both these articles get a copy of that file in their output directory. This is wasteful. We want to dedup this eventually.
There's a few ways this could work:
/files/sha2hash.extension, all articles then symlink to that file with the desired filename.The first option probably makes sense? I'd need to investigate how this influences caching too.