shubhamkakkar

file=path/to/websiteVersion.json

increment_patch_version='increment_patch_version'
increment_fix_version='increment_fix_version'
increment_feature_version='increment_feature_version'

commandToRun=${1:-increment_patch_version}

featureVersion=`cat ${file} \
  | grep featureVersion \

shubhamkakkar

wversion: 2.1

node_image: &node_image
  docker:
    - image: node:12

android_image: &android_image
  docker:
    - image: reactnativecommunity/react-native-android

shubhamkakkar

version: 2
aliases:
  - &restore-yarn-cache
    name: Restore cached root node_modules
    key: yarn-cache-{{ checksum "yarn.lock" }}
  - &save-yarn-cache
      name: Save node_modules to cache
      key: yarn-cache-{{ checksum "yarn.lock" }}
      paths:
        - node_modules  

shubhamkakkar

// make sure you have not installed react-native vector icons by now

make a file named react-native.config.js, content should be following
```
module.exports = {
    projects: {
      ios: {},
      android: {},
    },
    assets: ['./assets/fonts'],

shubhamkakkar

The Problem

Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)

The temptingly easy but ultimately wrong solution:

Alter the port the script talks to from 8000 to 80:

}).listen(80);