npm start: this will run build/dev-server.js, which is a basic script that compiles Pug, Stylus and JS deps (browserify)
To run with the mainnet config, do node build/dev-server.js --mainnet
To run the production build, you can follow the steps to build and then do http-server dist
Before deploying, please ensure
- To bump the version
- Make sure you're deploying the right configuration (Mainnet vs ropsten)
- Ensure you configure the NGINX proxy with a working ipfs hash to the right network (mainnet vs ropsten)
gulp --mainnet
And then, in the dexy-infra repo:
./deploy-scripts/app.sh USER@WEB_SERVER_IP
If you also want to deploy to IPFS, do:
ipfs add -r dist
gulp --ropsten
ipfs add -r dist
Ropsten:
Qme6GF9AuhyJ8BGhKT6gXMa83dt8KBDDyFgbqLejZtYms9 - commit hash c2f17d4b04475ded31be611f557f05b382e94f93
Update tokens list:
./scripts/genTokensList.js > ./configs/tokens/index.json
TODO
basically add them to src/js/routing and add a template/controller
As of commit hash 49a3ccf9fe716d63f955795941a76bda9f19bed3 the size of all dependencies, minified, is 1.8M - that contains a number of node modules (e.g. buffer) and web3, hdkey, ethereumjs-wallet
Currently, the way we update data is pretty messy
src/js/services/user: deals with user.ethBal, which is split in onWallet and onExchange - respectively how much ETH we have on our wallet and on the exchange's vault
src/components/exchange/exchange.js: deals with exchange.onWallet and exchange.onExchange, which is the current selected token balance on wallet and on the exchange's vault
Also emits the event reload-orders, which triggers a reload of orderbook, myOrders and tradeHistory controllers
src/components/exchange/myOrders: loads user's orders and updates exchange.onOrders, which are the ETH/token balances reserved on orders
src/components/exchange/orderbook: loads the entire orderbook
src/components/exchange/tradeHistory: loads the entire trade history