Am 24.02.2017 um 14:50 schrieb Moritz Maxeiner:
On Friday, 24 February 2017 at 11:22:34 UTC, Sönke Ludwig wrote:
[...]
Would be good if someone could have a look. Once this is merged,
anyone can run this on a server using `./dub-registry --mirror
https://code.dlang.org/` and then forward incoming requests using a
reverse proxy to http://127.0.0.1:8005.
To be clear: Would the argument need to be specified for every launch,
or is this a one-time call to set it up for future mirroring?
Is the mirrored data stored in a permanent location?
On every launch, there is already a configuration file, so adding
support for storing it there could be an alternative. The package
database is stored in a MongoDB instance on localhost currently (creates
a "vpmreg" collection).
In the current form, this will enable manual fallback in the form of
users specifying --registry=https://some.code.dlang.mirror on the DUB
command line. In the future we can then keep a list of official
mirrors as DNS entries (maybe of the form mirror1.dub.pm) and let DUB
use those automatically.
Cool, I'll see about setting one up when a new release of dub-registry
with that is out.
