Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically cleanup databases in listing.json #100

Closed
noqcks opened this issue Aug 9, 2023 · 2 comments
Closed

Automatically cleanup databases in listing.json #100

noqcks opened this issue Aug 9, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@noqcks
Copy link
Collaborator

noqcks commented Aug 9, 2023

What would you like to be added:

When doing xeol db list, there is a long list of listings returned, it's overwhelming for human eyes. Our listing.json should only contain something like the last 3 months of databases, even though we will keep an archive of all database listings.

Why is this needed:

Bad UX

@noqcks noqcks added the enhancement New feature or request label Aug 9, 2023
@noqcks noqcks self-assigned this Aug 9, 2023
@nidepapa
Copy link

nidepapa commented Nov 9, 2023

per this issue, should we clean the db data in local file or just set up a time constraint like (only list db with 3 months)?

@noqcks
Copy link
Collaborator Author

noqcks commented Nov 9, 2023

Hi @nidepapa!

Some context, we have a lambda that pulls data from endoflife.date every 24 hours and then uploads a sqlitedb to S3. The listing.json contains the databases and their timestamps and is updated with each lambda run. xeol db list shows the results from this listing.json file.

So, actually this ticket is misplaced, since the work needs to be done on the database creation lambda rather than the client. Unfortunately, the repo for this is not open-sourced yet. I think i'm going to close this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants