This is the frontend Vue.js application for the AVA Wallet.
- Recent version of npm (6.13.4)
- Node v12.14.1
- Gecko, AVA client in Golang (https://github.com/ava-labs/gecko)
- Clone the repo
git clone https://github.com/ava-labs/wallet-site.git
- Go to root of the project
cd wallet-site
- Install javascript dependencies with
npm install
. - Copy the example file
.env.example
, and rename it.env
. Fill the variables with the correct values. Refer to the ENV FILES section for additional help.
Make sure to read the official Vue environment variables document to get an understanding
of how it works for development and production (https://cli.vuejs.org/guide/mode-and-env.html). Vairables
beginning with VUE_APP_
will get injected into the vue application.
Refer to .env.example
VUE_APP_AVA_IP
The ip address of the Gecko jrpc node.VUE_APP_AVA_PORT
The port of the Gecko jrpc node.VUE_APP_AVA_PROTOCOL
Either http or httpsVUE_APP_NETWORK_ID
What is the network id of the AVA network you are connecting to.VUE_APP_CHAIN_ID
The blockchain id of the AVA Network you are connecting to.
Make sure to rebuild the project using npm run serve
after changing the .env
file.
In order for the wallet to work, it needs the AVA network to operate on.
- Make sure you have installed and able to run a Gecko node properly.
- Run the project with hot reloading
npm run serve
When you go to the website on your browser, you might get a warning saying "Site is not secure". This is because we are signing our own SSL Certificates. Please ignore and continue to the website.
- Setup environment variables for production
- Compile and minify to have a production ready application with
npm run build
. - Serve from the
/dist
directory.
We suggest using Google Chrome to view the AVA Wallet website.
Firefox does not allow https requests to localhost. But the AVA Wallet uses https by default, so we will need to change this to http. Make this switch by editing the vue.config.js
file in the root directory and change
devServer: {
https: true
},
to
devServer: {
https: false
},
and run npm run serve
to reflect the change.