Microsoft Azure offers cheap, reliable servers, virtual machines, and container services.
This deployment method can be used to jump-start your journey to your BridgeChain in the process outlined here.
You will end up with the following:
We will be using a setup available at our GitHub.
Navigate to: https://github.com/ArkEcosystem/ark-azure Click on the big blue “Deploy to Azure” button to be taken to Portal.Azure.com. Login with your account (trial or not, either will work).
You should only need to input data for three empty fields (Resource Group, Admin Password, and DNS Label), but full details for this section:
Create Newis the only option that will work unless you wish to edit the template yourself. We will use My-Ark-RG for this guide.
Currently, the VM produced is a Standard_A1 size VM. This is a very low-cost resource VM for tutorial purposes (can be scaled-up after deployment if desired or via template adjustment)
Purchase to begin deployment. The entire process should take 5–10 minutes.
You are welcome to explore your new VM’s Overview by clicking on
Resource Groups and finding your new group, and the VM inside. There are lots of configuration items here.
If you do not remember your Public DNS name or IP address (for SSH), go to:
Resource Groups >
Overview. This has all the general information you will need.
The Public DNS Name for all VMs follows this pattern: PublicDNSname.locationid.cloudapp.azure.com
So in this case, it would be here:
SSH into your new VM using the Public DNS Name and log in with the credentials used during the VM Template deployment page.
Run the following command (It’s a one-liner, copy and paste the full contents from here or from the Ark Azure Github page)
curl -o- https://raw.githubusercontent.com/ArkEcosystem/ark-azure/master/script/arkdefaultinstall.sh | bash
This script will complete all of the installation steps to get both the node and explorer running for your BridgeChain, with all the default values. Total installation time is about 10 minutes.
There is 1 essential item to locate in the stream of data being output to the console (for wallet control). Your Genesis Passphrase details!
Just after the node gets installed, there will be three lines of text to record. Copy these lines outlined in red below.
This information will be used later on, as you explore Ark past the deployment phase with Ark Deployer. Please copy and paste it right out of the console window for safe keeping.
This is the Public IP of your server, and the port required to view the Ark Explorer for your BridgeChain (4200). The API should be available on port 4100.
You can highlight the URL straight from the SSH window, such as http://188.8.131.52:4200 and hit CTRL+C to copy it. Paste into a browser, and voila!
If you wish to customize your deployment of Ark within the bounds of Ark Deployer, download a copy of the Azure Shell script.
Within this file, you’re welcome to edit the list of variables on lines 21–31 and personalize them. These variables all align with an optional parameter of Ark Deployer (See GitHub: optional parameters)
You can then run this new version of your script against a new VM, or, you can uninstall the original node/explorer and re-install using the script again. We would recommend just rolling out a new server for ease of use, but that’s your call.
Click on “Raw” on the same line as your file name and copy the URL.
On the VM, run the following to execute the new deployment.
curl -o- paste-raw-gist-URL-here-ending-in.sh | bash
Special thanks to Walrusface for writing the original guide and script, Delegate Jarunik for sponsoring its development and our developer Alex Barnsley for testing and modifying necessary things in Ark deployer. c