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

Convert project to monorepo #126

Open
gnarea opened this issue Jul 23, 2020 · 0 comments
Open

Convert project to monorepo #126

gnarea opened this issue Jul 23, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@gnarea
Copy link
Member

gnarea commented Jul 23, 2020

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.
  • etc...

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.

@gnarea gnarea added the enhancement New feature or request label Jul 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant