This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app). # Deployment Portal Frontend ## install required packages - Node.js ```cmd brew install node ``` - Yarn ```cmd brew install yarn ``` ## Available Scripts In the project directory, you can run: ### Install ```cmd yarn install export NODE_OPTIONS=--openssl-legacy-provider yarn start ``` - Above commands run the app in the development mode. - You can open [http://localhost:3000](http://localhost:3000) to view it in the browser. - The page will automatically reload if you make edits in the source code. - You will also see any lint errors in the console. ### Test ```cmd yarn test ``` - Launches the test runner in the interactive watch mode.
- See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information. ### Build ```cmd yarn 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](https://facebook.github.io/create-react-app/docs/deployment) for more information. ### Eject yarn 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. ## Some more steps before the portal works expectedly - get dump of RDS from any team member and execute the following steps docker rm pgsql --force docker run -d --name pgsql -p 5432:5432 -e POSTGRES_PASSWORD=admin -e POSTGRES_DB=deployment_portal postgres:11 cat <