ceejbot
commented
5 years ago We've been discussing this feature and its meaning a lot in the last day or so. Some notes from this discussion:
- Mirroring another registry's index is different from mirroring its content.
- Only top-level package metadata is mutable, and that comes with a date stamp. Package-versions are immutable and so are content blobs. (Immutability is so nice.)
- Chris says: The content isn't too much of a problem when broken out by content hash as we're doing. It's not so much "I want to request deps from 3 registries" as "I want to get legacy's definition of $FOO, entropic's definition of $BAR, and jan's definition of $BAZ, and then download the content for all of these from $WHEREVER"
- As soon as the registry see a remote dep in a package published to it, it must walk it and mirror its content. Installation stays kinda-local as far as content blobs go.
It should be easy (eventually; possible is a good start) to point one entropic instance at another and make a read-only mirror of its packages. Perhaps the packages would go under a namespace that is the sitename of the site being mirrored?