bitcasino-v3 v1.147.3

Please configure your VS Code to autocorrect code using tslint

Required plugins for VS Code:

• Prettier - Code formatter
• TSLint

{
  "prettier.tslintIntegration": true,
  "editor.tabSize": 2,
  "tslint.enable": true,
  "tslint.autoFixOnSave": true,
  "editor.formatOnSave": true
}

Please install volta.sh. Good software

Go to volta.sh and follow instructions. Take yarn and node versions from package.json and do:

# for example
volta install node@12.18.3 yarn@1.22.4

Working with branches

When starting work on a new feature, create your new feature branch from live branch.

When done developing your feature, create a pull request into develop branch. develop branch is automatically built and deployed to test4. Any further changes to your feature must follow the same flow - use the same feature branch.

Avoid merging branches other than live into your feature branch. That way you keep your feature separately deployable.

To create a new release, merge the desired feature branches to release or hotfix. You can also merge the whole develop branch at once if you're sure it doesn't contain any undesired features. Last commit's message should start from fix: or feat: for semantic-release to be able to build a new version. A new version tag will be built automatically and slackbot will provide the buttons to deploy it to staging and prelive on #bitcasino-site-dev channel.

After a new version has been deployed to live run yarn update-branches commnand. That way live, master, hotfix and release branches always will be in proper sync with live version.

Hotfix branches must be created from live or hotfix branches and commits should be pushed to hotfix branch via pull request.

Same but may be a bit outdated manual: https://coingaming.atlassian.net/wiki/spaces/BIT/pages/470024335/Bitcasino+Deployment

Creating new styled components

Follow the order of css properties:

1. Positioning

• position, z-index, top, right, bottom, left

2. Display & Box Model

• display, overflow, width, height, margin, border, padding

3. Other styles

• Avoid: regular font color (black/white), it's declaread in a root already | margin-top | selectors with nesting depth more then 3 (Ex. div > div > p > span) | em units | px after 0
• color: Avoid named and HEX colours. Use \${Colors.*}
• font-weight: Use only predefined \${Fonts.Weight.*}
• font-size: Use only predefined \${Fonts.SIZE-*}

Removing merged branches

git branch -r --merged | grep -v master | sed 's/origin\///' | xargs -n 1 git push --delete origin

For just testing

1. Load latest code

git pull

2. Run tests

yarn prod
yarn ui-manual-tests

(Ensure that "yarn proxy" is running from tests folder -- it should start automatically.)

3. Create new tests

Look into tests/cypress/integration/screens folder for examples

4. Save tests code

git add .
git commit -a --message="Added new tests"
git push origin develop

Looking at test4 docker logs

All test4 logs now in kibana under bitcasino-dev-* stack. Could be reached out via link:

https://monitoring.heathmont.net/logs/p/app/discover#/?notFound=search&notFoundMessage=Could%20not%20locate%20that%20search%20(id:%2012febc60-5171-11ea-8e0c-e93db0e84900)&_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-15m,to:now))&_a=(columns:!(_source),filters:!(),index:bitcasino-dev,interval:auto,query:(language:kuery,query:''),sort:!())

Checking and restarting services at test4

TODO: add portainer information

Manual:

export DOCKER_HOST=test4.casino.testenv.io
# take container pid
docker ps | grep graphql-gateway
# and kill it
docker kill pid

Deploying custom tag to prelive, staging

git tag -a bc-my-custom-tag-name
git push --tags

cd path/to/stacks/repo
git checkout staging
# put your changes to proper places and push to same branch
# you'll see your changes in deploy tool

Environment variables

Run the app

App could run in several modes: yarn dev - via webpack-dev-server with watch and hmr yarn watch - webpack builds server and client in a watch mode and run server via nodemon yarn prod - webpack builds makes production optimized build and run server via node without watch

App could run for different envs and projects. Check scripts section of package.json.