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

chore: new seed-db command #311

Merged
merged 3 commits into from
Jun 10, 2023
Merged

chore: new seed-db command #311

merged 3 commits into from
Jun 10, 2023

Conversation

vnugent
Copy link
Contributor

@vnugent vnugent commented Jun 9, 2023

Issue #309

I haven't figured out an automated way to redact emails so for the time being I manually exported the staging db, redacted emails manually and upload the new db file to google storage.

@vnugent vnugent marked this pull request as ready for review June 9, 2023 19:25
@vnugent vnugent requested review from zichongkao and musoke June 9, 2023 19:29
README.md Show resolved Hide resolved
@vnugent vnugent merged commit 4d0d590 into develop Jun 10, 2023
REMOTE_FILE="https://storage.googleapis.com/openbeta-dev-dbs/$FILE_NAME"

echo "Downloading db file(s)..."
#wget --content-disposition $REMOTE_FILE
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vnugent did you mean to comment this line out? yarn seed-db was failing since openbeta-stg-db.tar.gz wasn't actually getting downloaded.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ooops, good catch. Please uncomment it. Better yet, if you can improve the script so that we can either: download and rebuild db, or rebuild only (skip the download because it's a large file)

Copy link
Contributor

@siman4457 siman4457 Jun 19, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uncommented for now.

For improving the script:
Should the decision to download or skip download be from user input?

We can automatically start a download if we detect the tar file is outdated. Can we perform any versioning or date comparison between what's on Google storage and what we have locally?

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

Successfully merging this pull request may close these issues.

3 participants