-
Notifications
You must be signed in to change notification settings - Fork 116
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
Jekyll index in Elasticsearch is out of date #1197
Comments
@bfabio Agree with you, not a coincidence. That makes me think about this dualism that always leads us to problems. Page building phase and search should be based on same data, same source. |
100% agree. The wonky build system we have will is causing more pain than it should |
Looks like we need https://github.com/italia/developers.italia.it/runs/6382644010?check_suite_focus=true#step:7:54 |
* Use https://api.developers.italia.it to get the software and publishers data * Push the very same data to the ElasticSearch server during the build. This reduces/eliminates the problem with ElasticSearch having different data, see italia#1197 Fix italia#1290.
* Use https://api.developers.italia.it to get the software and publishers data * Push the very same data to the ElasticSearch server during the build. This reduces/eliminates the problem with ElasticSearch having different data, see italia#1197 This took months of refactoring, restructuring and redesigning, but it's done now. 😢 Fix italia#1290.
* feat: use the API to get software data * Use https://api.developers.italia.it to get the software and publishers data * Push the very same data to the ElasticSearch server during the build. This reduces/eliminates the problem with ElasticSearch having different data, see #1197 This took months of refactoring, restructuring and redesigning, but it's done now. 😢 Fix #1290. * feat: add static redirs for retrocompatibility Add static redirs to maintain the URLs based on old software slugs.
The Jekyll index in Elasticsearch is out of date:
It should be updated at build but it stopped on 04/13, which is also the day we switched to GitHub actions for building the site and that's certainly not a coincidence.
I'm guessing there's something wrong with the authentication to ElasticSearch (maybe wrong environment variables in the secrets?)
The text was updated successfully, but these errors were encountered: