Updating README.md

Author: Rizchel Dayao

MAINTAINERS.md

@@ -0,0 +1,69 @@
+# Maintainers Guide
+
+This guide is intended for maintainers - anybody with commit access to one or
+more Code Pattern repositories.
+
+## Methodology
+
+This repository does not have a traditional release management cycle, but
+should instead be maintained as as a useful, working, and polished reference at
+all times. While all work can therefore be focused on the master branch, the
+quality of this branch should never be compromised.
+
+The remainder of this document details how to merge pull requests to the
+repositories.
+
+## Merge approval
+
+The project maintainers use LGTM (Looks Good To Me) in comments on the pull
+request to indicate acceptance prior to merging. A change requires LGTMs from
+two project maintainers. If the code is written by a maintainer, the change
+only requires one additional LGTM.
+
+## Reviewing Pull Requests
+
+We recommend reviewing pull requests directly within GitHub. This allows a
+public commentary on changes, providing transparency for all users. When
+providing feedback be civil, courteous, and kind. Disagreement is fine, so long
+as the discourse is carried out politely. If we see a record of uncivil or
+abusive comments, we will revoke your commit privileges and invite you to leave
+the project.
+
+During your review, consider the following points:
+
+### Does the change have positive impact?
+
+Some proposed changes may not represent a positive impact to the project. Ask
+whether or not the change will make understanding the code easier, or if it
+could simply be a personal preference on the part of the author (see
+[bikeshedding](https://en.wiktionary.org/wiki/bikeshedding)).
+
+Pull requests that do not have a clear positive impact should be closed without
+merging.
+
+### Do the changes make sense?
+
+If you do not understand what the changes are or what they accomplish, ask the
+author for clarification. Ask the author to add comments and/or clarify test
+case names to make the intentions clear.
+
+At times, such clarification will reveal that the author may not be using the
+code correctly, or is unaware of features that accommodate their needs. If you
+feel this is the case, work up a code sample that would address the pull
+request for them, and feel free to close the pull request once they confirm.
+
+### Does the change introduce a new feature?
+
+For any given pull request, ask yourself "is this a new feature?" If so, does
+the pull request (or associated issue) contain narrative indicating the need
+for the feature? If not, ask them to provide that information.
+
+Are new unit tests in place that test all new behaviors introduced? If not, do
+not merge the feature until they are! Is documentation in place for the new
+feature? (See the documentation guidelines). If not do not merge the feature
+until it is! Is the feature necessary for general use cases? Try and keep the
+scope of any given component narrow. If a proposed feature does not fit that
+scope, recommend to the user that they maintain the feature on their own, and
+close the request. You may also recommend that they see if the feature gains
+traction among other users, and suggest they re-submit when they can show such
+support.

README.md

@@ -1,4 +1,4 @@
-# React-redux-api-example
+# Movie Finder
 
 This project calls the OMDb API to get information about a movie the user entered using React and Redux. 
 

README1.md

@@ -0,0 +1,81 @@
+# Deploy a React application on Kubernetes
+
+In this Code Pattern, we will deploy a React application using Kubernetes.
+
+There are many choices when looking for the right solution to manage and deploy our applications. It can often be overwhelming when we're trying to pick the right solution. One of our many choices is Kubernetes. This pattern will take you through how to get a front end application deployed on Kubernetes. After implementing the code, you will have the knowledge to deploy your own applications on Kubernetes. 
+
+This repository uses the React JavaScript library to build out the front end of the application. Redux is a predictable state container used hand in hand with React. The OMDb API is used to get movie information based on user input. It handles all of the state management within the application. Docker is an open source tool that is used to package the application into a container. Kubernetes handles the management and deployment of the containerized application.
+
+When the reader has completed this Code Pattern, they will understand how to:
+* Containerize a React application using Docker
+* Deploy and manage an application using Kubernetes
+
+## Flow
+
+## Included components
+* IBM Cloud Container Service: IBM Bluemix Container Service manages highly available apps inside Docker containers and Kubernetes clusters on the IBM Cloud.
+* Kubernetes Cluster: Create and manage your own cloud infrastructure and use Kubernetes as your container orchestration engine.
+
+## Featured technologies
+* Node.js: An open-source JavaScript run-time environment for executing server-side JavaScript code.
+* Cloud: Accessing computer and information technology resources through the Internet.
+* Containers: Virtual software objects that include all the elements that an app needs to run.
+* Container Orchestration: Automating the deployment, scaling and management of containerized applications.
+
+# Watch the video
+
+# Steps
+Use the ``Deploy to IBM Cloud`` button **OR** run locally.
+
+## Run locally
+> NOTE: These steps are only needed when running locally instead of using the ``Deploy to IBM Cloud`` button.
+
+1. [Clone the repo](#1-clone-the-repo)
+2. [Retrieve an api key for OMDb API](#2-retrieve-an-api-key-for-omdb-api)
+3. [Containerize the application using Docker](#3-containerize-the-application-using-docker)
+4. [Deploy the application on Kubernetes](#3-deploy-the-application-on-kubernetes)
+
+### 1. Clone the repo
+
+Clone the `react-redux-api-example` locally. In a terminal, run:
+
+```
+$ git clone https://github.com/rizcheldayao/react-redux-api-example.git
+```
+
+### 2. Retrieve an auth key for OMDb API
+
+You must get an API key from http://www.omdbapi.com/ in order to get a response from the API. You will insert your API key in /src/actions/index.js on line 42
+
+### 3. Containerize the application using Docker
+
+In a terminal, run the following commands: 
+
+```
+$ docker build -t <your_docker_username>/react-redux-api-example .
+```
+
+```
+$ docker run -p 3000:3000 -d <your_docker_username>/react-redux-api-example
+```
+
+### 4. Deploy the application on Kubernetes
+
+In a terminal, run the following commands:
+
+```
+$ bx cr namespace-add <your_namespace>
+```
+
+```
+$ bx cr build -t registry.<region>.bluemix.net/<your_namespace>/react-redux-api-example:v1 .
+```
+
+```
+$ docker tag react-redux-api-example registry.<region>.bluemix.net/<your_namespace>/react-redux-api-example:v2
+```
+
+```
+$ docker push  registry.<region>.bluemix.net/<your_namespace>/react-redux-api-example:v2
+```
+