view release on metacpan or  search on metacpan

lib/DarkPAN/Resolver/SQLite.pm  view on Meta::CPAN

leading C<+> (take-the-name-verbatim):

--resolver +DarkPAN::Resolver::SQLite,<mirror-url>

C<< <mirror-url> >> is the public base URL of your DarkPAN (the same URL a
browser or C<cpanm --mirror> would use), for example
C<https://cpan.openbedrock.net/orepan2>. The resolver fetches the index from
C<< <mirror-url>/modules/packages.db.gz >>.

Only a public HTTP(S) URL is required -- the resolver uses L<HTTP::Tiny> and does
B<not> need AWS credentials or S3 access, even for an S3-backed DarkPAN fronted
by CloudFront. (HTTPS requires L<IO::Socket::SSL>/L<Net::SSLeay> to be present,
as with any C<HTTP::Tiny> https use.)

=head1 HOW IT WORKS

On construction the resolver fetches C<modules/packages.db.gz> from
the mirror, decompresses it to a temporary file, opens the SQLite
database, and uses it only for package lookups.

=over 4

share/README.md  view on Meta::CPAN

leading `+` (take-the-name-verbatim):

\--resolver +DarkPAN::Resolver::SQLite,<mirror-url>

`<mirror-url>` is the public base URL of your DarkPAN (the same URL a
browser or `cpanm --mirror` would use), for example
`https://cpan.openbedrock.net/orepan2`. The resolver fetches the index from
`<mirror-url>/modules/packages.db.gz`.

Only a public HTTP(S) URL is required -- the resolver uses [HTTP::Tiny](https://metacpan.org/pod/HTTP%3A%3ATiny) and does
**not** need AWS credentials or S3 access, even for an S3-backed DarkPAN fronted
by CloudFront. (HTTPS requires [IO::Socket::SSL](https://metacpan.org/pod/IO%3A%3ASocket%3A%3ASSL)/[Net::SSLeay](https://metacpan.org/pod/Net%3A%3ASSLeay) to be present,
as with any `HTTP::Tiny` https use.)

# HOW IT WORKS

On construction the resolver fetches `modules/packages.db.gz` from
the mirror, decompresses it to a temporary file, opens the SQLite
database, and uses it only for package lookups.

- 1. selects all rows for the requested package from the index;