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

v2 alpha: start using v2 search/results #540

Open
8 of 9 tasks
Tracked by #456
maxachis opened this issue Nov 26, 2024 · 2 comments
Open
8 of 9 tasks
Tracked by #456

v2 alpha: start using v2 search/results #540

maxachis opened this issue Nov 26, 2024 · 2 comments

Comments

@maxachis
Copy link
Contributor

maxachis commented Nov 26, 2024

Part Of:

Requirements

Then, we will be in an alpha state where we have the v2 app and API using the v2 database, fed from Airtable. We can have users test the search, and celebrate the user-friendliness.

Meta goals

  • Ensure we have a means to quickly switch back, if necessary
    • we can revert to a previous deployment/branch, because v1 will still be live; I don't think we need to use a feature flag here
  • Ensure that other parts of the website, still under development, are not exposed
    • covered by the above requirements

1

Footnotes

  1. I didn't have the heart to delete all Max's footnotes

@maxachis maxachis changed the title start using v2 search/results (I think the db is stable enough for that) start using v2 search/results Nov 26, 2024
@josh-chamberlain josh-chamberlain changed the title start using v2 search/results v2 alpha: start using v2 search/results Nov 26, 2024
This was referenced Nov 26, 2024
@maxachis
Copy link
Contributor Author

@josh-chamberlain I've set up the v1->v2 database refresh to occur daily, rather than every hour -- we can technically do it (and I know I previously was like "Sure, let's do it!") , but I will need to make some adjustments to the automation server to make sure it's properly cleaning out old builds, because it'll build up more quickly otherwise.

Other than that, what's the rationale for having it refresh hourly, rather than daily, considering we don't typically have super fast-updating source data?

@josh-chamberlain
Copy link
Contributor

@maxachis that's ok! No real rationale—in cases where we do have a handful of folks making submission (it happens) it can be nice to see the effects of your work in the same day. Really, daily is perfectly fine.

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

No branches or pull requests

3 participants