Build the API in Github Actions and store images in ghcr.io#79
Draft
Build the API in Github Actions and store images in ghcr.io#79
Conversation
Contributor
Author
|
This is in theory ready to merge, but will require some work to get deployed. Will look at it after summer. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is so we can have better version control of what backends are on what API versions
This will make it much easier to separate out API backends, and colocate them with elasticsearch/logstash for searching - still need to decide how far to take that.
Separate logstash containers for each backend would make things easier, since they could then use the same file mounts as the API to ingest data to elasticsearch. Separate elasticsearch containers may be a bit too much, since it requires a fair amount of resources and would be trickier to manage via Kibana if there's one for each project/publication.