This is the official React template for CGM - Charlie Meyer's React Template.
- Overview
- Getting Started
-
Overview of Files
- A general file structure is provided below.
- Contributing
This is a template for creating a new CRA project created by Charlie Meyer. It is based upon the Create React App (CRA) template.
This includes the following:
To create a new project using this template, run the following command:
npx create-react-app my-app --template cgmTo start the development server, run the following command:
npm startThis runs the app in development mode in Port 8080 (see the command PORT 8080 in start within package.json). Open http://localhost:8080 to view it in the browser. Port 8080 is chosen and it is also used in the Dockerfile and nginx.conf, so if you change it here, you will need to change it in those files as well (I think).
To build the app for production, run the following command:
npm run buildThis 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.
However, the dockerfile, nginx.conf, and deploy.yml file have been included to build and upload the image to GCR, with a template example of deploying to Google Cloud Run, so you can use that instead of npm run build.
If you want to build a docker image, run the following command:
docker build -t <image-name> .This builds the docker image with the name specified. The image is based on the nginx:alpine image and serves the static files from the build folder. The nginx.conf file is copied into the image and the default.conf file is replaced with it. The default.conf file is the nginx configuration file that is used to serve the static files.
To run the docker image, run the following command:
docker run -p 8080:80 <image-name>This runs the docker image on port 8080. You can then open http://localhost:8080 to view it in the browser. However, you can automate this using the deploy.yml file within the .github/workflows folder written for your CI/CD pipeline. See the section .github/workflows for more information.
The file structure of this template is as follows:
my-app
├── .github
│ └── workflows
│ └── deploy.yml
├── public
│ ├── index.html
│ ├── robots.txt
│ └── manifest.json
├── src
│ ├── app
│ │ ├── App.css
│ │ ├── App.js
│ │ ├── firebase.js
│ │ ├── RouteLocations.js
│ │ └── store.js
│ ├── assets
│ ├── components
│ ├── hooks
│ ├── pages
│ │ ├── aboutPage
│ │ │ ├── assets
│ │ │ ├── components
│ │ │ ├── AboutPage.css
│ │ │ ├── AboutPage.js
│ │ │ └── utils.js
│ │ ├── homePage
│ │ │ ├── assets
│ │ │ ├── components
│ │ │ ├── HomePage.css
│ │ │ ├── HomePage.js
│ │ │ └── utils.js
│ │ └── errorPage
│ │ ├── assets
│ │ ├── components
│ │ ├── ErrorPage.css
│ │ ├── ErrorPage.js
│ │ └── utils.js
│ ├── slices
│ ├── utils
│ └── index.js
├── trash
├── .gitingore
├── Dockerfile
├── nginx.conf
├── package-lock.json
├── package.json
└── README.md
There are some folders that have markdown files in them explaining their purpose that are not shown in this folder structure.
The workflow file included in the .github/workflows folder is used to build and upload the docker image to GCR. There is then an example of how to deploy it to Google Cloud Run (it super simple, fastest way to deploy your app), but you may also add any other deployment you would like (Google Kubernetes Engine, Google App Engine, etc).
Make sure to add repository secretes to your GitHub repository for the following:
- PROJECT_ID - The ID of your Google Cloud Project
- GCP_SA_KEY - The service account key for your Google Cloud Project
For further security, you may include REGION, SERVICE_NAME, IMAGE_NAME, and other variables as secrets as well. The only one that is absolutely required for safety is GCP_SA_KEY. Ensure that when creating the Service Account key through the Google Cloud Console, you give it the proper (but minimal) permissions to upload, read, and deploy your images.
This is the main HTML file that is served to the client. It is based on the default index.html file that is created by CRA, with some modifications.
Rather than using static images for the favicon and the apple-touch-icon, it uses a converter that converts emojis into svg's, seen here. If you do add static images, make sure to add them to the public folder, change the links accordingly, and update the manifest.json file to include the image in the icons array.
Robots.txt is a file that tells search engine crawlers which pages or files the crawler can or can't request from your site. This is a default robots.txt file that is used for most sites. If you want to change it, you can do so there.
The manifest.json file is a JSON file that tells the browser about your Progressive Web App and how it should behave when installed on the user's desktop or mobile device. This is a default manifest.json file that is used for most sites. If you want to change it, you can do so there.
This is the main CSS file for the entire app. There are some simple styles included in this file from Josh's Custom CSS Reset, but you may add any other styles you would like here.
If you want to add custom colors, fonts, or others, add them to the :root selector in this file, and then you can use them in any other CSS file in the app. For example:
App.css
:root {
--primary-color: #000000;
--secondary-color: #ffffff;
--font-family: "Roboto", sans-serif;
}SomePage.css
.someClass {
color: var(--primary-color);
font-family: var(--font-family);
}You can also add the styles to everything in the app by adding them to the body selector in the App.css file or by adding them to the * selector in the App.css file. Using these variables and using them consistently throughout the app will make it much easier to change the look and feel of the app later on, if you want to change color schemes, add a dark/light mode toggle, change fonts, etc.
This is the main JavaScript file for the entire app. It is based on the default App.js file that is created by CRA, with some modifications. This includes basic routing using React Router.
This file is commented out by default if the user does not want to use firebase, but if you do, simply create a firebase project at https://firebase.google.com/ and add the config to this file. Then, uncomment the file and you can use firebase in your app. You can import them into any other file in the app using the following:
import { db, auth } from "../path/to/firebase.js";Firebase is an easy database to use for quickly building, but popular tech-stacks such as the PERN stack (PostgreSQL, Express, React, Node) are also great options. If you want to add similar ease-of-use with authentication and database access using the PERN stack, you can use authentication libraries such as Passport.js and database libraries such as Sequelize to achieve similar results.
This is a simple javascript object that holds all of the paths for the routes. This should be updated as you add, change, and remove routes in the App.js file. By using this RouteLocations.js file instead of hardcoding the paths, simply editing routes once in RouteLocations.js will update them everywhere in the app. To use it, import it into any file you need it in using the following:
import { RouteLocations } from "../path/to/RouteLocations.js";
import { useNavigate } from "react-router-dom";Then, in your JSX, you can use RouteLocations to navigate the user to the correct page. For example:
const navigate = useNavigate();
...
<Link to={RouteLocations.home}>Home</Link>
<div onClick={() => navigate(RouteLocations.home)}>Home</div>This folder configures a store that is then imported and used in index.js. There are no reducers added to the store, but you can add them accordingly as shown in the comments in the file. Here is an example of store.js file with a reducer for 'user.'
import { configureStore } from "@reduxjs/toolkit";
import userReducer from "../slices/userSlice";
const store = configureStore({
reducer: {
user: userReducer,
},
});
export default store;It is highly recommended to use Redux DevTools with this store, simply download the extension from the Google Chrome Web Store and it will automatically connect to the store. You may then view the state of the store and dispatch actions to the store from the extension.
This assets folder holds assets that are used across the entire app. This can include images, fonts, or other things. Avoid putting all of your assets into this folder - assets used only in one component or one page should be put in the assets folder in that component or page.
This folder holds all components that are used across the entire app. This can include buttons, modals, or other things. Avoid putting all of your components into this folder - components used only in one page should be put in the components folder in that page.
Furthermore, the folders of each component should be in camelCase, and the file names should be in PascalCase. For example, a component called 'My Component' should have a folder called 'myComponent' and a file called 'MyComponent.js'.
This folder houses any custom hooks created for the app. While it is best practice to put hooks in the folder for which they are being used, for ease of use, you can put all custom hooks in this folder, each in a separate file.
All the pages that are used in this app are housed in this folder. Each page has its own folder, each with a CSS file, JS file, a utils.js, a components folder and an assets folder (if necessary). You should remove the folders/files that are not being used - they are suggestions for best practice. The CSS file should be named the same as the page, and the JS file should be named the same as the page, but in PascalCase. For example, a page called 'My Page' should have a folder called 'myPage' and a file called 'MyPage.js'.
It is recommended that the file structure of your pages folder follows the file structure of your routes. For example, if you have a route called '/my-page', you should have a folder called 'myPage' in the pages folder, and a file called 'MyPage.js' in that folder. However, for small-scale applications, this is not necessary.
This folder contains all of the slices that are used in this application. It is best to group slices by an "idea," such as "user" or "posts."
Here is an example of a slice that stores the user's name and email address:
import { createSlice, createAsyncThunk } from "@reduxjs/toolkit";
// add functions, asyncThunks, and other logic above here.
export const createUserInDatabase = createAsyncThunk(
"user/createUserInDatabase",
async (user) => {
// add logic here to create user in database.
}
);
const userSlice = createSlice({
name: "user",
initialState: {
name: "",
email: "",
},
reducers: {
setName: (state, action) => {
state.name = action.payload;
},
setEmail: (state, action) => {
state.email = action.payload;
},
},
// you may add builder cases for asyncThunks here.
extraReducers: (builder) => {
builder.addCase(createUserInDatabase.fulfilled, (state, action) => {
// add logic here to update state after asyncThunk is fulfilled.
});
},
});
export const { setName, setEmail } = userSlice.actions;
export const selectName = (state) => state.user.name;
export const selectEmail = (state) => state.user.email;
export default userSlice.reducer;This folder contains any utility functions used across the entire app. If a page or component uses a util, it should be in its own folder in that page or component.
Here is the index.js file that is created by CGM CRA. This uses StrictMode, React Router, and Redux. It is recommended to use React StrictMode, but you can remove it if you wish.
import React from "react";
import ReactDOM from "react-dom";
import App from "./app/App";
import store from "./app/store";
import { Provider } from "react-redux";
import { BrowserRouter } from "react-router-dom";
const root = ReactDOM.createRoot(document.getElementById("root"));
root.render(
<React.StrictMode>
<Provider store={store}>
<BrowserRouter>
<App />
</BrowserRouter>
</Provider>
</React.StrictMode>
);This folder is where you can put any trash. It is recommended not to delete code, but to put it in this folder. This way, if you need to reference it later, you can. If you are sure you will not need it, you can delete it.
This simple dockerfile is used to create a docker image for the app. It is not necessary to use this, but it is recommended.
This file is used to tell git which files to ignore. It is recommended to use this file, but you can delete it if you wish.
This file is used to configure nginx. It is not necessary to use this, but it is recommended.
If you would like to contribute to this project, please fork the repository and create a pull request. If you have any questions, please email me at charlie@charliemeyer.xyz.