Bug#1020217: S3-backed snapshot implementation
On 06/05/24 at 14:40 +0200, Simon Josefsson wrote:
> Lucas Nussbaum <lucas@debian.org> writes:
>
> > - I got the OK to host a S3-backed snapshot mirror using the Debian AWS
> > account (see thread in #1020217)
>
> Is this s3 bucket public, or will it be?
It's my plan to make it public, yes
> I have been worried about the state of snapshot and I am mirroring its
> data into local Git LFS. Since snapshot.debian.org doesn't support
> rsync and don't make the postgres database dumps available (so that I
> can identify SHA1 objects and speed up downloads), I am using HTML web
> scraping to find out what files exists to snapshot.d.o.
If you are a DD, you could:
ssh lw08.debian.org psql service=snapshot-guest -c '\\dt'
List of relations
Schema | Name | Type | Owner
--------+---------------------+-------+----------
public | archive | table | snapshot
public | binpkg | table | snapshot
public | config | table | snapshot
public | directory | table | snapshot
public | farm_journal | table | snapshot
public | file | table | snapshot
public | file_binpkg_mapping | table | snapshot
public | file_srcpkg_mapping | table | snapshot
public | indexed_mirrorrun | table | snapshot
public | mirrorrun | table | snapshot
public | node | table | snapshot
public | removal_affects | table | snapshot
public | removal_log | table | snapshot
public | srcpkg | table | snapshot
public | symlink | table | snapshot
(15 rows)
The 'file' table is the one that lists all known hashes.
Lucas
Reply to: