aboutsummaryrefslogtreecommitdiff
path: root/README.org
diff options
context:
space:
mode:
authorChristopher Baines <mail@cbaines.net>2022-02-04 12:21:18 +0000
committerChristopher Baines <mail@cbaines.net>2022-02-04 12:21:18 +0000
commit6457dd4d9ed35762685b18be74712101a1be5287 (patch)
tree755d1fe4967e3905aa3cab919ba863b286d238a5 /README.org
parentf016f37ee004294722650ac570d3e4286bc8d161 (diff)
downloadnar-herder-6457dd4d9ed35762685b18be74712101a1be5287.tar
nar-herder-6457dd4d9ed35762685b18be74712101a1be5287.tar.gz
Add a bit to the design in the README
Diffstat (limited to 'README.org')
-rw-r--r--README.org4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.org b/README.org
index 87d97bd..567c745 100644
--- a/README.org
+++ b/README.org
@@ -32,7 +32,9 @@ facilitate things like tagging the narinfos and doing garbage
collection like tasks. Plus, because the narinfos are quite small, I
believe storing them in a database is actually more performant and
efficient than storing them as files on the filesystem, even with the
-duplication that comes with the database schema being used.
+duplication that comes with the database schema being used. It's also
+easier to copy all the narinfos between machines when you can download
+a single "database", rather than copying the files individually.
Secondly, while tools like NGinx work great as a reverse proxy for the
nar files, proxying the requests for the narinfo files can be