We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We should eventually convert this repo to a monorepo to make it easier to maintain and manage its artefacts.
We could arrange the components based on the artefact they output, instead of having a single Docker image as the only output artefact:
crc-cogrpc
pdc-pohttp
crc-incoming-queue
key-management
We shouldn't be too granular to begin with to minimise complexity. For example, the two crc-* components could be one at the start.
crc-*
Consider using https://rushjs.io/ to manage the monorepo.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We should eventually convert this repo to a monorepo to make it easier to maintain and manage its artefacts.
We could arrange the components based on the artefact they output, instead of having a single Docker image as the only output artefact:
crc-cogrpc
, the server for the CogRPC binding as a Docker image.pdc-pohttp
, the server for the PoHTTP binding as a Docker image.crc-incoming-queue
, the background job that processes incoming cargoes, as a Docker image.key-management
, a script to generate/rotate/revoke identity (RSA) and session (ECDH) keys.We shouldn't be too granular to begin with to minimise complexity. For example, the two
crc-*
components could be one at the start.Consider using https://rushjs.io/ to manage the monorepo.
The text was updated successfully, but these errors were encountered: