You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two problems with using the alpine package:
The version can change out from underneath us
It doesn't necessarily have all the algos we need to test against turned on.
For CI purposes, we should be building from source so that all the algos we need are guaranteed to be on.
We should be using a multistage build for this and copying the built library over into the image. To verify that the image is good when we set up the dockerfiles, we should manually do a ponylang/crypto clone and make test run to verify it all works as expected.
The text was updated successfully, but these errors were encountered:
Our other libressl environment uses whatever version of libressl that
alpine's package manager installs. This new environment is tied to a
specific version of libressl that we build from source.
This gives us more control over what is tested and when we change
what is tested.
Closes#10
Our other libressl environment uses whatever version of libressl that
alpine's package manager installs. This new environment is tied to a
specific version of libressl that we build from source.
This gives us more control over what is tested and when we change
what is tested.
Closes#10
There are two problems with using the alpine package:
For CI purposes, we should be building from source so that all the algos we need are guaranteed to be on.
We should be using a multistage build for this and copying the built library over into the image. To verify that the image is good when we set up the dockerfiles, we should manually do a ponylang/crypto clone and make test run to verify it all works as expected.
The text was updated successfully, but these errors were encountered: