-
Notifications
You must be signed in to change notification settings - Fork 19
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
Restructure the repo files #3079
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Kai,
Since it is mostly restructuring, I tested it by checking out the code locally, building the node and the identity worker and launching in standalone mode. It looks good. I could do all basic operations like retrieve/ link identity and request vc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a nice improvement 👍🏼
Context
As topic, this is now the tree structure:
And in
tee-worker
:A root-dir can only have one workspace definition.
It would be very chaotic and incredibly long deps if I have one big
Cargo.toml
that specifies deps for both parachain and workers.So I'm going to have a workspace definition for parachain and worker, respectively. The
common
will then come up as standalone crates.Note
Workers still have isolated directories - I don't want to introduce too many changes in one PR. A bigger PR will follow up with workspace-dependencies for workers.
Warning
Please note the changes (in case anything needs to be changed in the deployment script) @m1iktea