This project was bootstrapped with Create React App.
In the project directory, you can run:
REACT_APP_API_ENDPOINT=<app-server-host:port> npm start
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.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
- Install docker https://docs.docker.com/get-docker/
- Add
ENV REACT_APP_API_ENDPOINT=http://localhost:<local-port-of-server>
in your dockerfile - Build Docker image from the application root:
docker build -t <image-name> .
- Run your image using below command:
docker run -dp <local-port>:<application-port> <image-name>
- To check that your application is running, enter url
http://localhost:<exposed-port>
-
Install kubectl cli
-
Point to the correct cluster, set your KUBECONFIG env variable to the kubeconfig file provided in the project root.
-
Run below kubectl commands from project root to deploy the application on the above mentioned kubernetes cluster.
kubectl create -f deployment-task-manager-ui.yaml
kubectl create -f service-task-manager-ui.yaml
kubectl create -f secret-task-manager.yaml
-
The above steps will create application in default namespace. You may append
-n <namespace>
in the command if you wish to deploy in some other namespace. -
Once the Application is deployed, you will see your application exposed through an External IP by the k8s Load Balancer. Currently the application is exposed on port 8080. We can enhance it further by enabling SSL. To get the external IP of the application by running following command.
kubectl get svc
NOTE: One instance of this application is already running on oracle cloud. You may access it using this URL
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.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify