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

Jekyll index in Elasticsearch is out of date #1197

Closed
bfabio opened this issue May 11, 2022 · 3 comments · Fixed by #1198 or #1199
Closed

Jekyll index in Elasticsearch is out of date #1197

bfabio opened this issue May 11, 2022 · 3 comments · Fixed by #1198 or #1199
Assignees
Labels

Comments

@bfabio
Copy link
Member

bfabio commented May 11, 2022

The Jekyll index in Elasticsearch is out of date:

$ curl -u $ELASTIC_USERNAME:$ELASTIC_PASSWORD http://localhost:9200/_cat/aliases
jekyll    jekyll-20220413112043
[...]

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?)

@bfabio bfabio added the bug label May 11, 2022
@bfabio bfabio self-assigned this May 11, 2022
@sebbalex
Copy link
Member

@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.

@bfabio
Copy link
Member Author

bfabio commented May 11, 2022

100% agree. The wonky build system we have will is causing more pain than it should

@bfabio
Copy link
Member Author

bfabio commented May 11, 2022

Looks like we need ELASTICSEARCH_URL set - (which we already have? 🤔 not really, we need to pass the secrets in the action)

https://github.com/italia/developers.italia.it/runs/6382644010?check_suite_focus=true#step:7:54

bfabio added a commit to bfabio/developers.italia.it that referenced this issue May 11, 2022
bfabio added a commit to bfabio/developers.italia.it that referenced this issue May 11, 2022
bfabio added a commit to bfabio/developers.italia.it that referenced this issue May 11, 2022
@bfabio bfabio reopened this May 11, 2022
bfabio added a commit to bfabio/developers.italia.it that referenced this issue Jun 12, 2024
* 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.
bfabio added a commit to bfabio/developers.italia.it that referenced this issue Jun 12, 2024
* 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.
bfabio added a commit that referenced this issue Jun 12, 2024
* 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants