# Go-zenon deploy script for public testing
**URL:** https://forum.hypercore.one/t/go-zenon-deploy-script-for-public-testing/491
**Category:** Development
**Created:** [September 19, 2024, 5:16pm UTC](https://forum.hypercore.one/t/go-zenon-deploy-script-for-public-testing/491 "2024-09-19T17:16:17Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@0x3639](https://forum.hypercore.one/u/0x3639)
#### Post date: [September 19, 2024, 5:16pm UTC](https://forum.hypercore.one/t/go-zenon-deploy-script-for-public-testing/491/1 "2024-09-19T17:16:17Z")
The [Operations Special Interest Group (SIG)](https://zenon.wiki/index.php/HC1:_Operations_SIG) has been working on a bash script to simplify the process to deploy a `go-zenon` node. The script is being made available today for public testing.
The script can be used to deploy, build, restore, and monitor `go-zenon`. Over the coming weeks we plan to enhance the script to add additional functionality. We will plan to add timeseries monitoring, advanced troubleshooting, and the ability to launch a testnet.
Today we are asking for public testing and feedback on the script. The goal is to deploy `go-zenon` and then deploy the grafana monitoring stack. You will be able to monitor the underlying node (vps) and certain `znnd` metrics.
## Instructions
### Clone the Repo
`git clone https://github.com/hypercore-one/deployment.git`
### Move into that Repo
`cd deployment`
### Make the script executable
`sudo chmod +x go-zenon.sh`
### Execute the script
`sudo ./go-zenon.sh`
First the script will install all the necessary packages. Then it will ask you which repo to clone. Select `enter` for the default repo. That is the `/zenon-network/go-zenon` repo. We plan to change how this works in the future.
After `go-zenon` is built and started then you can install the monitoring package.
### Install Grafana
`sudo ./go-zenon.sh --grafana`
In order to see the metrics navigate to `http://IP_OF_VPS:3000`
Note we use `http` and NOT `https`. The default username is `admin` and the default password is `admin`. Change the password and look for the default dashboard setup. There are two.
Please provide feedback on the experience and let us know if you have any recommendations for improvement or change. You can also submit issues or feature requests here: [GitHub · Where software is built](https://github.com/hypercore-one/deployment/issues)
---
### Author:  [@edgepillar](https://forum.hypercore.one/u/edgepillar)
#### Post date: [September 19, 2024, 8:40pm UTC](https://forum.hypercore.one/t/go-zenon-deploy-script-for-public-testing/491/2 "2024-09-19T20:40:04Z")
Just built one. Super easy and working like a charm so far!
---
### Author:  [@coinselor](https://forum.hypercore.one/u/coinselor)
#### Post date: [September 19, 2024, 9:27pm UTC](https://forum.hypercore.one/t/go-zenon-deploy-script-for-public-testing/491/3 "2024-09-19T21:27:32Z")
Ran this over a working/synced zenon node. Worked without issues.
Minor stuff I noted:
- Missing line break at `ption":"","path":"","removed":false}Installation and configuration completed successfully. `
- I wasn’t sure if the grafana dashboard was going to work while the znnd node was still initializing. There’s a loading animation but maybe we can add ‘Loading…’ or ‘Connecting…’ placeholder.
I also had to add 3000 to ufw so I could connect in this particular VPS, but I know the script is not touching firewalls yet.
Will try with vilkris branch from scratch.
---
### Author:  [@Turmin](https://forum.hypercore.one/u/Turmin)
#### Post date: [June 2, 2025, 11:26am UTC](https://forum.hypercore.one/t/go-zenon-deploy-script-for-public-testing/491/4 "2025-06-02T11:26:43Z")
Thanks for this one!
Since the script is only tested for x86, I ran into a few obstacles while installing it on ARM64.
First, I had to modify go-zenon.sh to accept and download the ARM64 version of Go. That was the easy part — the node is now running (I don’t have a Pillar yet).
The bigger challenge was getting the Grafana Dashboard to work. It relies on Prometheus (by the way, there’s a typo in the dashboard: it says “Promotheus”) and node\_exporter, both of which are installed as x86 binaries by default. I replaced them with their ARM64 counterparts.
In the end — everything is running like a charm!
Edit: I forgot to mention that I used Vilkris repo for this.