Add support for separate Horizon deployment #37
Merged
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.
I found we need to make sure a queue worker (Horizon) starts, otherwise certain things dont work (i.e. deleting posts). While I opened this PR for the docker image, as Matt notes, it'd probably be better for scalability to run it in a separate deployment.
Changes in MR:
ENABLE_HORIZONenv var to true.Values.pixelfed.horizon.separate_deploymentis true, createdeployment_backend.yamlwhich deploys the same app image, but with an overridden command/args to run Horizon explicitly (related docs suggesting this for compose). I've also removed some env vars that I don't expect to need for that process. More cleanup may be possible.We could make this the default, but for complexities sake, might not be worth it