Create a tutorial, in the form of an article or a video, on how to automatically deploy and boot your own NEAR network, using it to test a new release of nearcore.

As a user, I should be able to follow the tutorial and boot a NEAR localnet in my network. This tutorial will explain how to use `nearup localnet` properly, providing additional ways to test new releases of nearcore and test a CI/CD pipeline without running real nodes on BetaNet or TestNet.

Bounty: 1500

Maintenance: 10%

Link: https://github.com/nearprotocol/stakewars/blob/master/challenges/challenge005.md

Create a tutorial, in the form of an article or a video, on how to automatically deploy and boot your own NEAR network, using it to test a new release of nearcore.

As a user, I should be able to follow the tutorial and boot a NEAR localnet in my network. This tutorial will explain how to use `nearup localnet` properly, providing additional ways to test new releases of nearcore and test a CI/CD pipeline without running real nodes on BetaNet or TestNet.

Bounty: 1500

Maintenance: 10%

Link: https://github.com/nearprotocol/stakewars/blob/master/challenges/challenge005.md

Create an article and a Github document/script to explain and execute an automated deployment of a new release of nearcore. This contribution is close to the previous one (Release a CI Pipeline), with the difference that you will have to automate the deployment and the testing of a new release.

As a user, I should be able to follow the instructions in this doc to automatically deploy the new nearcore release, starting from a compiled artifact (which ideally is created via CI pipeline). There are no limitations in terms of platforms and tooling to use, and no specific limitations between docker and no-docker alternatives.

This is a great opportunity to prove your proficiency with CI/CD tools, and serve NEAR community with an open-source tool that everyone can use and improve.

Bounty: 3000

Maintenance: 15%

Link: https://github.com/nearprotocol/stakewars/blob/master/challenges/challenge005.md

Create an article or a commented Github script to explain and execute an automated building and testing of a new release of nearcore.

As a user, I should be able to follow the instructions in this doc to automatically generate the executable binary of nearcore from a new release on Github. There are no limitations in terms of platforms and tooling to use, and no specific limitations between docker and no-docker alternatives.

This is a great opportunity to prove your proficiency with CI tools, and serve NEAR community with an open-source tool that everyone can use and improve.

Bounty: 3500

Maintenance: 15%

Link: https://github.com/nearprotocol/stakewars/blob/master/challenges/challenge005.md

Create an article or a commented Github script to explain and execute an automated building and testing of a new release of nearcore.

As a user, I should be able to follow the instructions in this doc to automatically generate the executable binary of nearcore from a new release on Github. There are no limitations in terms of platforms and tooling to use, and no specific limitations between docker and no-docker alternatives.

This is a great opportunity to prove your proficiency with CI tools, and serve NEAR community with an open-source tool that everyone can use and improve.

Bounty: 3500

Maintenance: 15%

Link: https://github.com/nearprotocol/stakewars/blob/master/challenges/challenge005.md

Create an article or a commented Github script to explain and execute an automated building and testing of a new release of nearcore.

As a user, I should be able to follow the instructions in this doc to automatically generate the executable binary of nearcore from a new release on Github. There are no limitations in terms of platforms and tooling to use, and no specific limitations between docker and no-docker alternatives.

This is a great opportunity to prove your proficiency with CI tools, and serve NEAR community with an open-source tool that everyone can use and improve.

Bounty: 3500

Maintenance: 15%

Link: https://github.com/nearprotocol/stakewars/blob/master/challenges/challenge005.md

Create an article or a commented Github script to explain and execute an automated building and testing of a new release of nearcore.

As a user, I should be able to follow the instructions in this doc to automatically generate the executable binary of nearcore from a new release on Github. There are no limitations in terms of platforms and tooling to use, and no specific limitations between docker and no-docker alternatives.

This is a great opportunity to prove your proficiency with CI tools, and serve NEAR community with an open-source tool that everyone can use and improve.

Bounty: 3500

Maintenance: 15%

Link: https://github.com/nearprotocol/stakewars/blob/master/challenges/challenge005.md

Create an article or a commented Github script to explain and execute an automated building and testing of a new release of nearcore.

As a user, I should be able to follow the instructions in this doc to automatically generate the executable binary of nearcore from a new release on Github. There are no limitations in terms of platforms and tooling to use, and no specific limitations between docker and no-docker alternatives.

This is a great opportunity to prove your proficiency with CI tools, and serve NEAR community with an open-source tool that everyone can use and improve.

Bounty: 3500

Maintenance: 15%

Link: https://github.com/nearprotocol/stakewars/blob/master/challenges/challenge005.md