Advice/Steps for building HollaEx Kit to Dev

Step 1) Don’t build on your local machine…you’ll need to upload it all the dependencies in order to run on your site anyways. SO SAVE YOUR TIME, but here is a compiled list if you’d like to follow to help speed up your build. (NOTE: If you do decide to build on your local machine, DON’T FORGET to START DOCKER HUB FIRST!!!) <=Before Anything!
Step 2) ADVISE: Create a AWS EC2, stay away from DigitalOcean, they’re good but AWS is better for developers.
Okay here is my list to help just copy and paste in order…After you create your EC2, forgive some of the over simplification of what you may be reading in the 'DOCS" here is just a copy paste list from start to finish, as I have seen many posts about Docker fails. So starting from the beginning of the “DOCS” you will see where you need to enter docker and docker-compose, I have laid out a list of commands for you to build from, just copy and paste. This was written for Ubuntu. NOTE BOS> = Beginning of script, and <EOS = End of Script, copy and paste all attributes in-between, do not un-stack the code. AS FOLLOWS…

A). git clone
B). cd hollaex-kit
C). bash
D) sudo apt-get update

E) BEG> sudo apt-get install
lsb-release <END

Add Docker’s official GPG key

F). BEG> curl -fsSL | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg <END


G) BEG> echo
“deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg]
$(lsb_release -cs) stable” | sudo tee /etc/apt/sources.list.d/docker.list > /dev/nulll <END

_____Install Docker Engine

H). sudo apt-get update

I). sudo apt-get install docker-ce docker-ce-cli

J). docker ps

Install Docker Compose___

K). BEG> sudo curl -L “$(uname -s)-$(uname -m)” -o /usr/local/bin/docker-compose <END

L). sudo chmod +x /usr/local/bin/docker-compose

M). sudo ln -s /usr/local/bin/docker-compose

N). docker-compose -v

Again I can’t emphasize this enough…Avoid installing on your local machine.
There are some funny things about the software that will frustrate you, like NGINX falling off in the proxy. So if you just build in the cloud and ignore all the localhost prompts including localhost/v2/health in your terminal, and get all the way to “hollaex prod” you will have a working site.
I hope this helps.

SIDE NOTE DISCLAIMER BEFORE YOU BUILD AND DEPLOY TO THE MAIN-NET: For those in the USA, please be aware that building an financial exchange and deploying it with out the proper Federal Registration is Felony and Punishable by Jail, and Fines, and in addition you will never be able to transmit money as a business ever again once you get out of jail. So get licensed!!! The laws in question are pertaining to the ,“Onboarding” Federal MTL, AML, MBS, and State Guidelines. Too many people are going to get in big trouble, look up the man who got fined $60 Million USD for not properly following the guidelines of the MTL.
So building it is perfectly fine, deploying to the main-net, not so much if you are not in compliance, consult your attorneys…This is financial software!

Average Minimum Time To Get Licensed Fully: 6 Months! Cost Minimum 15-30K That is just Federal, Each state requires different bonds, and registration fees. When all is said and done, you could expect to shell out $500K for licensing alone, and that is every year. Don’t get lulled into a false sense that you can make it rich by just deploying an exchange, SEC won’t see it that way.

1 Like

Hi! These are detailed and useful steps. Thank you so much for sending these in! :slight_smile:

1 Like

Admin please delete my post, I fear it is going to confuse more than help. I can’t seem to delete it myself.

1 Like