This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

`npm start`

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

`npm test`

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

`npm run build`

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

`npm run eject`

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Web

To run locally on linux systems create kind cluster with haproxy, load this application image in that (for testing locally) configure metallb for load balancing, specify namespace, metallb,secret and configmap with specific ports.

build container with docker

docker build -f Dockerfile -t sargam-web:latest .

test it out and run docker run -it -p 3000:3000 sargam-web:latest

setup kind k8s cluster for local development

apply kind config

kubectl config use-context kind-dev-py

kind create cluster --name dev-py --config kind-example-config.yaml kind load docker-image sargam-web --name dev-py

kind delete cluster --name dev-py

setup metalb for load balancing

setup metallb instructions

kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.9.3/manifests/namespace.yaml kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.9.3/manifests/metallb.yaml

On first install only

kubectl create secret generic -n metallb-system memberlist --from-literal=secretkey="$(openssl rand -base64 128)"

now run kubectl get nodes -o wide see the IP range

kubectl get nodes -o wide

run this and keep the IPs different from the above IP range cause in the above IP range those are the nodes.


apiVersion: v1
kind: ConfigMap
metadata:
  namespace: metallb-system
  name: config
data:
  config: |
    address-pools:
    - name: default
      protocol: layer2
      addresses:
      - 172.18.0.220-172.18.0.250
EOF

apply deployment and services to k8s cluster

kubectl apply -f deployment

deploy using helm charts

helm install sarweb chart

Chitrank-Dixit/sargam-web

Available Scripts

npm start

npm test

npm run build

npm run eject

Learn More

Code Splitting

Analyzing the Bundle Size

Making a Progressive Web App

Advanced Configuration

Deployment

npm run build fails to minify

Web