This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may 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.
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
Available Docker Compose v0.0.0
To create .env
with environment variables
docker compose up
docker compose down
Development with Server & Client v1.0.0
# install packages
$ npm install
# running Express
$ node index.js
# root of client
$ cd client/
# install packages
$ npm install
# running React
$ npm run start
- Create an account on Heroku (now you should fill up the form of Billing Information)
- Install the Heroku CLI
- Login with account on terminal (you might need to create authorization in Account settings)
- Set engines in package.json for Specifying a Node.js & an npm Version
- Set scripts in package.json for Customizing the build process
- Use Heroku CLI set environment variables in production
- Then
git push
certain branch to publish the project
# rook of repository
$ git push heroku main
- Deploy React and Express to Heroku
- When NPM miss with Heroku, How To Solve (npm ERR! Failed at the start script).
- Create a Web Service to connect repository on Render.
- Fill up relative settings in Docker environment.
- Set Environment Variables on target service.
- Go to following Process.
Method 2. - Blueprint Specification
- Create
render.yaml
for Web Service setting in repository. - Create a new Web Service to connect repository on Render.
- Set Environment Variables on target service.
- Go to following Process.
- Folder
/client
for front end client. - Folder
/
for back end server. - Dockerfile implementing for building web service.
- copy
package*.json
to root directory - install packages for server in root
- copy
/client
to/client
directory - set environment for front end(optional)
npm run build
to build client files for server service
- copy
# go to folder client
$ cd client
# install packages for React App
$ npm install
# go back to root
$ cd ..
# install packages for Express App
$ npm install
# run server in port 3030 & client in port 3000
$ npm run start
or you can execute independently
# run server in port 3030
$ npm run server
# run client in port 3000
$ npm run client