massalabs / massalabs/node-manager-plugin
scripts to download latest node versions
Nobody has claimed this yet.
- #3 by @0xB19 — closed without merging
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In a /scripts folder we should have 3 script, one for each OS, that :
- download the node from links exposed in the doc : https://docs.massa.net/docs/node/install
- uncompress it
- rename the folder node-massa
- inside the node-massa folder keep only the massa-node folder (delete massa-client)
- duplicate massa-node
- rename one of them mainnet
- rename the other buildnet
- retrieve the buildnet conf from https://raw.githubusercontent.com/massalabs/massa/buildnet/massa-node/base_config/config.toml (this is inspired from https://github.com/massalabs/docs/blob/d6625369a7d1654747718e37a9db1ea210e4c0f0/scripts/download-configs.sh#L59) and replace the base_config/config.toml content of the buildnet dir by the the downloaded content
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the node installation links in the Massa documentation and the referenced docs/scripts/download-configs.sh example. Create the three OS-specific scripts under /scripts, covering download, extraction, directory setup, and buildnet configuration retrieval. Done means each script produces mainnet and buildnet node-massa directories with the requested contents and configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100