Whole bunch of config for an isomorphic React application

Notes:

• Node v10.14.1 at the time of writing
• make build-image and make push both use jq, a json parser which must be installed with brew install jq
• runserver.js pulls env conf out of json files defined in a .env directory and assigns them to process.env much like the dotenv module. runserver.js also runs webpack programmatically to build and watch the bundle as well as starts and watches the dev server with babel bindings. runserver.js --mode production seamlessly plugs into the deployment pipeline and simply starts the pre-transpiled server.js assuming the bundle is also compiled

Clone the repo git clone [email protected]:richytong/react-isomorphic-boilerplate

Install dependencies npm i

Run the application node runserver.js

Navigate to http://localhost:3000

Ensure your aws cli is configured

aws configure

# or save a specific config profile
aws configure --profile YOUR_PROFILE_NAME

Run make

make

Makefile

• DOCKER_REGISTRY_URL - url to your docker registry, for example 211133300000.dkr.ecr.us-east-1.amazonaws.com
• DOCKER_IMAGE_NAME - name of the docker image, usually the module name
• VERSION - pulled directly from package.json.version

make

• clean removes old build files
• build-source builds source and bundle
• build-image builds docker iamge
• push auths and pushes to remote docker repository

redux is a predicatable state container for Javascript apps. Predictable in its declarative approach to state management using Actions, plain Javascript object payloads that send data to the application store with store.dispatch(action), and Reducers that take these Actions and specify how the application's state changes in response (previousState, action) => newState. Reducers often switch on action.type to predictably and declaratively change the application state like so:

const myReducer = (previousState = [], action) => { // our application state is an array
  switch (action.type) {
    case 'SOME_ACTION_TYPE':
      const newState = action.data
      return newState;
    default:
      return state;
  }
};

Application state is declared in the reducer in this manner using the default function parameters. For more complex applications however, it is more practical to split up reducers into multiple more specific ones. Redux provides a utility called combineReducers that allows you to easily declare multiple reducers for different parts of your state:

const myReducerForA = (previousState = initialA, action) => action.newA;
const myReducerForB = (previousState = initialB, action) => action.newB;
const myReducerForC = (previousState = initialC, action) => action.newC;

// the following are equivalent
const entireReducer = combineReducers({
  a: myReducerForA,
  b: myReducerForB,
  c: myReducerForC,
});

const entireReducer = (state = {}, action) => ({
  a: myReducerForA(state.A, action),
  b: myReducerForB(state.B, action),
  c: myReducerForC(state.C, action),
})

All combineReducers() does is generate a function that calls your reducers with the slices of state selected according to their keys. The state for the above application would then be { a: someA, b: someB, c: someC }. Actions, Reducers

redux-thunk middleware allows you to write action creators that return a function instead of an action so you have more control when composing your redux actions. Abstract away network control flow to a thunk. You can also write normal action creators that return state. See the docs