From HollaEx Kit 1.2.1 To 1.3

This update contains significant flow improvements at setting up the exchange, huge performance update for the web server, general bug fixes and increased stability.

A user could set up various exchange configurations with a clean UI, at the admin panel. If you are having a technical difficulty, you could now invite others (your tech team, or even bitHolla team) to help you set up the exchange.

Please check the changelog for more information on these changes.

Pulling the latest HollaEx Kit

HollaEx Kit relies on Git for managing and hosting code and supports Git commands for managing your repo for the new updates. git pull origin master is pretty much the entire process for updating your kit. Follow this guide to avoid code conflicts and making sure that the update goes as expected.

Committing changes

git add -A && git commit -m "my-commit-message"

Before starting, commit and changes you've made to your kit.

Checking the Git Remote

git remote -v

You always should check your Git Remote URL for your HollaEx Kit before pulling it. If the result is you can proceed to the next step.

But If it's pointing a different repository, You should set it to point Official HollaEx Kit repo first, before pulling it. You can set the remote repo by using the command below.

git remote set-url origin https://github.com/bitholla/hollaex-kit.git

Pulling the latest Kit

git pull origin master

This command will pull the latest Kit from GitHub. Current latest version is v1.3.

If you changed the Git Remote URL by using git remote set-url, you should revoke it to the old one at this step. Use git remote set-url <YOUR_GIT_REPO_URL> first, before proceed.

Resolving conflicts

You might face some conflicts due to the changes you made on your HollaEx Kit, including settings files configurations. Fix the conflicts through your code editor. You will most likely face conflicts with these four files:

  • settings/configmap - Configmap file for HollaEx Exchange configuration.

Configmap

The conflict happened above is caused by a new HollaEx Core version number specification. The latest Core version compatible with the latest 1.3 Kit is 1.22.0. Accept the incoming change to apply it.

For the secret file, It would be related with the password update for default backend components. Starting from the Kit 1.3, the default passwords would be set as empty on Kit level, and the HollaEx CLI would generates them on-the-fly for better security.‌

Since you already initialized the exchange, you should keep them as your existing values. Accept the current changes.

Depends on user's setup and configurations, the part causing conflicts could be different. Please review them all clearly, and solve the conflict.

Upgrading HollaEx Core

hollaex upgrade

This command will upgrade your exchange's HollaEx Core to the latest v1.22.0, which is only compatible with HollaEx CLI v1.9+. The latest version of CLI would be installed along with the Core upgrade automatically. If you are on HollaEx CLI 1.9 already, this step would be passed by itself.

Once the CLI upgrade is done, run hollaex upgrade again to upgrade the HollaEx Core to the latest v1.22.0.

Follow the upgrade process with the CLI. Once it's all done, you'll be able to see the new HollaEx Core version number has been changed at /v1/health API endpoint. You could also use hollaex status command to check the status briefly.

Troubleshooting

If something went wrong, you can ask questions at bitHolla Forum with printed error logs to get a community's help.