I am happy to announce the release of confmgr. You may visit the repo, directly install its NPM package or follow me for a gentle introduction.
1. The problem There are several ways to manage various configurations in your NodeJS App. One of them is about using Environment Variables.
Invoking your index.js as follow:
MY_VAR1=42 node index.js makes MY_VAR1 available to your script with the following code:
I introduced srtool in a previous article. While the first implementation filled a gap and allowed for the first time users to verify substrate runtime wasm blobs, there was still work to do to improve the user’s experience.
1. Current verification process Up to now, the verification process looked like:
a runtime dev works on some changes
he builds the new runtime locally, preferably using srtool in order to get the SHA256 of the new wasm blob right away
There is no question that Rust is one of the, if not THE, best language of the decade.
Rust allows us writting safe code while doing most of the safety checks at compile time. That means that we no longer need to bloat the binary that is produced with extra checks to safeguard against developer mistakes such as null and dangling pointers or overflows to mention just a few.
ssh is the defacto standard to access a remote server. It does not offer much of a point and click GUI but get things done with a fair level of security.
ssh shows however a major drawback: it is based on TCP.
You will likely never notice any issue until you connect to a server over ssh from a train, a plane or from a mobile device, and briefly lose your connection, or if your device switches network such as going from the Wifi to your Cellphone connection and switching back to Wifi.
Unlike all other Blockchains, Polkadot (based on Substrate) allows on-chain protocol upgrades without requiring the node operators to do anything but to keep their node up and running.
If you know everything about Substrate Runtime, you may jump to the Installation section.
In order to achieve this, Polkadot stores its runtime executable as a WASM blob in its own storage. If the WASM blob is replaced, the new runtime kicks in and all the nodes start using it, altogether.
In order to interact with the Ethereum Blockchain and the best levels of security, one need to first have a running node that is fully synchronised. With the increasing traffic on Ethereum, this is becoming more and more difficult for regular users to stay in sync. This article introduces ethup, a simple tool that aims at doing just that.
Figure 1. Console output while synchronising the Ethereum Blockchain using parity ethup can be found on github at: https://github.
EthereumSoliditySnippets is a set of SublimeText snippets for the Ethereum Solidity contract language.
Use Control Package to install.
This package requires the great package from davidhq: https://github.com/davidhq/SublimeEthereum to recognize solidity code.
To get started, create a .sol file. SublimeText will then recognize your file as an Ethereum Solidity file and activate the syntax coloriring as well as the snippets.
To see the list of available snippets, open the Panel (Shift+Command+P) and type 'solidity'.
Chocolatey package for Ethereum. This allows (un)installing the client on windows as you would with homebrew or apt-get.
You can visit the project page on GitHub.
The Github project for AlethZero is located at here.
You can find the list of available packages on chocolatey.org or read more about chocolatey.
Warning The latest version changes very often. The package downloads the latest. It means that unlike the chocolatey package may suggest, you are not installing THE version x.