Everything EOS Developer Series, 8 Nov 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Setting up LiquidApps' Zeus SDK, including NVM + NPM (Blockchain Dev Tools by Peter Keay)

Description

Advanced Blockchain Development Tools is an Everything EOS course sponsored by Cypherglass. Please vote for my sponsor! https://cypherglass.com

In this lesson, we set up Node.js, including Node Version Manager (NVM) for easy management of multiple versions of Node. Then, we use Node Package Manager to install the Zeus Software Development Kit, the easiest way to develop immortal dApps with DAPP Network services locally.

**IN THIS VIDEO**
01:06 Setting up Node Version Manager
03:22 Installing Zeus Software Development Kit

**More Everything EOS Developer Videos**
Learn more about EOSIO and DAPP Network development by visiting our Everything EOS Developer Series Playlist:
https://www.youtube.com/playlist?list=PLRK9ZLYOWiXPJ2ThcTpn4e9Y6MyqqY49r

Continue on to learn about vRAM in the next video (link posted soon).

**GETTING HELP**
Stay tuned for updates on this course's learning platform launch! For now, follow the playlist and reach out to the Everything EOS telegram or https://twitter.com/bitgensteinx with any issues or questions.

Sign up for occasional updates at https://everythingeos.io/dev

Take the first course, which teaches the basics of building a smart contract and dApp frontend in ReactJS+Redux+NodeJS and C++, at https://www.udemy.com/course/eos-blockchain-dapp-development-tutorial

A

Welcome back to the everything you know, some fans Palach chain development tutorial. Last time we were in terminal a lot working with Cleo's getting set up. Maybe you skipped that, if you're familiar with it well, this time we're gonna be back in terminal setting up node package manager NPM in order to do that, we're gonna set up a new version manager because you often want to work with different versions of node, and that will help you manage your node versions without having to uninstall and reinstall and basically deal with a mess.

A

The reason we're doing that is we're going to be setting up Zeus software development kit and Zeus. Like many software development tools requires node package manager. Its packages are handled by node package manager, which makes it really easy to install and setup and otherwise manage. So, let's go ahead right now and get ourselves to a terminal window and oops want to obviously make myself not so garganta in in there alright. So here we are in a terminal window. Now we're gonna need to do one complex command. We're gonna have to get this script.

A

Sadly, even though we just set up homebrew in the last lesson, homebrew install is not recommended for node version manager, so we're gonna need to go to get this script. This nvm script and output it to bash. For me, it says it's already installed for you, it'll take a little bit and then at the end, it'll tell you these three commands. You can either close and reopen your terminal or you can run the following now.

A

Let's just run the following: now export the home directory I'm triple clicking to select entire lines here, load up in VM and then also the completion just for our convenience and I'll clear. The screen and you'll see over here that I actually have my current version of node that I'm using displayed. That's version.

A

13 Zeus software development kit, which we'll be using to set up all dab, Network services that we'll be taking advantage of, requires a node version of ten that you'll often run into software development tools that ask you to use a certain version of node. So for our convenience, we have installed node version manager and it's very simple- to tell node version man to install a version of node. Let's say we want the latest version, 10 all right, I go ahead and nvm install 10.

A

The latest version is downloaded and there we are we're using this version, 1017 of node, which will be good for our purposes of using Zeus software development kit. Now I can also install the latest node package manager just to make sure we're up to date, there and 18.5 seconds later I'm updated to the latest NPM.

A

Now, with node package manager installed, we can easily install a bunch of things. We're gonna need, let's install Zeus SDK the command for this is NPM install you're used to sub commands.

A

By now, if you're not very experienced with terminal- and you went through the Cleo's tutorial last lesson- you'll notice that we had Cleo sand then and then a sub command like maybe create, and then another sub command like key well node we've got NPM install and then we're gonna actually put the Zeus SDK here, but we want to install this globally so that we can access it from anywhere so that we can spin it up in various places, and we need to specify that it's at liquid, apps and I believe it's Zeus command like that now, just because we're installing it globally doesn't mean that everything will be available globally.

A

Zeus is an extensible framework. That's made up of boxes, you can create your own boxes. You can use pre-made boxes whatever, and the only command that will be available everywhere is unbox. Zeus unbox will let you unbox a box into the current directory you're in so once, Zeus is installed. We're gonna go ahead and unbox the hello world contract just to get a feel for how it works again. Zeus like so many other things, will run on sub commands.

A

So we'll say: Zeus unbox, a certain box, Zeus test Zeus migrate, Zeus deploy Zeus, compile whatever we need to do with Zeus SDK we've installed in forty seven point four nine seconds. So let's go into a VDT, and here I'm gonna make a directory called Zeus contracts, but that really wasn't the best directory named Zeus projects.

A

Okay, now in Zeus projects, there's obviously nothing here, but I want to unbox hello world here. So let's give it a go now, if you're on Linux you're gonna have to install some dependencies first on Mac, it works great without installing a bunch of dependencies. No, while this is going, I'm gonna go ahead and show you these commands.

A

Let's see where are they here all right here? So if you're on Ubuntu you'll have to do this stuff, you want to install C++ library and then this nonsense. If you're a developer, you might already have all this installed. If you're on CentOS or Fedora or AWS, then you need this prefix path for C make after installing, all this stuff and and then on, CentOS and Fedora, but not AWS. You've got some additional stuff to do here and not it won't.

A

Take you too long if you want to get to this link all I'll post it, along with the actual notes, since this kind of walks, through everything we're doing on the liquid apps blog we're still not done over here. I'm gonna wait and maybe speed this up a little bit.

A

Now one of the things that Zeus and the data general likes to do is is make sure that with one command you can do a lot of things you need. We've got MOCA unboxing for testing. We've got contracts, we've got USGS. Installing we've got crypto, we've got ipfs, let's see system contracts, all sorts of ego stuff going on, but it does take a while. So let's get back to it,.

A

Well caught me in the middle of drinkin: it actually finished hey there. We go seven and a half minutes, but it gives us a couple of sample commands to do to compile the sample contract to migrate to a local US laboratory which actually is managed by Zeus for us. So let's go ahead and hit migrate and watch what happens unknown argument. Oh yeah well, I obviously need to change directories into the unboxed box first and then I can migrate.

A

I'm gonna need to run docker if you haven't set up docker before go ahead and do so all right. My docker desktop is running now. I should be able to run Zeus migrate, so we didn't have the contract development toolkit installed and it'll do it for us. Rather than throwing an error message again, Zeus does try to allow you to do whatever you want with a single command. So here it check to whether the contract development toolkit is installed.

A

It's not so it's pulling it for us which again might take a little while of course, as soon as they get the guitar to pass the time it passes. That was only two and a half minutes and looks like it. Failed looks like it failed because I don't seem to have scenic installed, which doesn't make too much sense.

A

So, let's try to on a whim, brew, install see, make and that should have also set up the links for us so that we can run Zeus migrate and since we downloaded the contract development toolkit already, that won't have to happen. Hey. Alright, we're getting much farther here looks like we're good. It says we are done migrating now. If you remember on in the clearest tutorial, we did a Clio skate account, you know say: oh and because we weren't specifying an API endpoint.

A

It was going for a local node and trying to get information about the local yose blockchain. We couldn't do that because we didn't have one running, but now that we just sent one up. There is one running indeed, and it's got this development key and it's got. Some EEO sits its local I/o. So it's called sis to differentiate it's just on the development environment, and now we actually have a little block chain running thanks to Zeus SDK. So, let's actually run a full test now using Zeus tests again in the hello world directory.

A

Actually, if we, if we run Zeus as usual, we'll see a whole litany nevermind, we have to actually do help. It's not automatically clear, sir docker and that'll give us a whole litany of commands that we can experiment with and use in order to develop our contracts. Let's go ahead and do a Zeus test run. So the test runs a number of the same things, but it will also test the contract after it's deployed we're running a test on the encrypted key utility. Just to make sure everything is hunky-dory.

A

So Zeus migrate not only compiled the contract, spun up a local, no díos and also deployed it. It's also now running some tests. Local utility tests and also the hello world contract is getting tested as well. All the tests past looks like everything's ok, so we have successfully installed node version manager to install node package to get the zoo software development kits set up, which means now we can start easily adding DAP network services and easily doing other things like deploying front-ends to ipfs, with REO stops. So we'll start doing that next time by learning.