-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[MGX-355] Node improvements & cleanups #424
Conversation
mateuszaaa
commented
Feb 14, 2023
•
edited
Loading
edited
- improve sed cmd so its compatible with any docker image hardcoded
- Rename chainspecs: - 'kusama-mainnet' -> 'kusama' - 'local' -> 'kusama-local' - 'public-testnet' -> 'rococo' - 'mangata-rocococ-local-testnet' -> 'rococo-local'
- set alice as sudo in kusama-local chainspec
- assign corrent runtime name of the chainspec
- set Alice as sudo for rococo-local
- use new versioning convention that matches version from Github releases
- automatically build docker image that supports both mangata and kusama
- release single docker image for kusama & rococo
- Update readme file
- provide feelock palet genesis configuration
- update rococo & kusama chainspecs with genesis feelock configuration
- 'kusama-mainnet' -> 'kusama' - 'local' -> 'kusama-local' - 'public-testnet' -> 'rococo' - 'mangata-rocococ-local-testnet' -> 'rococo-local' Delete chainspecs: - 'dev'
9f2962b
to
0fbc046
Compare
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.
😎
cd ./launch | ||
yarn install | ||
yarn gen | ||
yarn up |
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.
can someone validate these steps? recently i had to call instead of the yarn gen
node_modules/.bin/parachain-launch generate
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.
I've tried it multiple times before and it was working fine.
That's how it is also being invoked in our pipeline.
@@ -175,10 +175,10 @@ pub const VERSION: RuntimeVersion = RuntimeVersion { | |||
spec_name: create_runtime_str!("mangata-parachain"), | |||
impl_name: create_runtime_str!("mangata-parachain"), | |||
authoring_version: 15, | |||
spec_version: 15, | |||
spec_version: 2800, |
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.
why such number ? v28.00 ?
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.
yep, more like 0.28.0, i expect 0.28.3 -> 0283
fd43a82
to
00769bb
Compare
00769bb
to
c85ee3b
Compare
f1ffcb4
to
beb42e4
Compare
bcd6927
to
9298a00
Compare
9298a00
to
6b8cc48
Compare
… feature/node-setup-cleanup
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.
🚀🚀🚀
That's very good, that we do this renaming on such early stage!