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

Always mount CA certificates and keys using in-memory files #299

Merged
merged 2 commits into from
Feb 1, 2022

Conversation

kegsay
Copy link
Member

@kegsay kegsay commented Jan 31, 2022

  • Remove VolumeCA as we don't mount the file as a volume anymore.
  • Remove COMPLEMENT_CA as we always mount regardless of whether or not the Homeserver image uses it.
  • Rejig when and where the CA cert/key is made. Now it is automatically made when a config.Complement is made.
  • Remove unused/redundant params for deployImage.

This can be optimised further. Currently, every time an image is deployed we inject the CA files. It would be sneakier to just do this once when a blueprint is made, so that way the files are already there when we deploy the container.

Fixes #65

- Remove `VolumeCA` as we don't mount the file as a volume anymore.
- Remove `COMPLEMENT_CA` as we always mount regardless of whether or not the Homeserver image uses it.
- Rejig when and where the CA cert/key is made. Now it is automatically made when a `config.Complement` is made.
- Remove unused/redundant params for `deployImage`.
@kegsay kegsay requested a review from neilalexander January 31, 2022 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider removing COMPLEMENT_CA and having it always on
2 participants