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

Refine s3 approach #80

Open
hcorson-dosch-usgs opened this issue Nov 10, 2022 · 0 comments
Open

Refine s3 approach #80

hcorson-dosch-usgs opened this issue Nov 10, 2022 · 0 comments

Comments

@hcorson-dosch-usgs
Copy link
Collaborator

Currently, the pipeline pushes the generically named 'gw-conditions-peaks-timeseries.csv' to the prod s3 bucket, and a version with the dates appended to the dev s3 bucket, for our records.

In #79 Cee has added a band aid so that we can manually point Vue to the correct file to use, controlling when the site is updated with new data. They dropped the 'gw-conditions-peaks-timeseries.csv' for wy22 into the prod bucket as 'gw-conditions-peaks-timeseries-wy22.csv' and pointed Vue to that file.

Currently, we can't just use the version w/ the dates in the filename because it is in the dev s3 bucket which cannot be accessed through a url in the browser.

As Cee notes, we need to refine this piece. We could redirect the file that includes the dates in its name to the public bucket instead of the dev as a solution. We definitely don't need to keep both the '-wy22' version and the version with the dates. Cee also notes that we should consider how long we should store these updates once we have a routine down.

We also need to consider how we can set the site up such that a) the user could select which dates are shown, and b) so that we can easily change the dates so that the page regenerates each month.

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

No branches or pull requests

1 participant