This is the frontend for the messaging app for the NGINX Microservices March demo architecture.

Note: This project is very much a WIP and is not yet up to the standards of the other projects included in this org as part of the NGINX Microservices March demo architecture.

This project uses NodeJS. The current version is specified in .tool-versions. NodeJS is a rapidly evolving language which makes it critical to explicitly define which version is being used to avoid any potential errors due to mismatched versions.

We recommended that you use asdf to manage your local NodeJS installation. Once you have asdf installed, you can run asdf install to automatically install the version of NodeJS specified in .tool-versions.

You can also install NodeJS by other means - just reference the version number in the .tool-versions file.

1. Clone this repo:

   git clone https://github.com/microservices-march/messenger-ui

2. Install NodeJS modules:

   npm install

In the project directory, you can run:

Open http://localhost:3000 to view the app in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

To run with mock data:

REACT_APP_MOCK_ENABLED=true npm start

To run with real data (assuming the messenger app is running and listening on port 4000):

REACT_APP_MOCK_ENABLED=false REACT_APP_BACKEND_HOST=localhost:4000 npm start

See the Create React App section on running tests for more information.

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 will be ready to be deployed once it's built!

See the Create React App section on 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 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.

If you want to cleanup any artifacts resulting from running this project, run:

rm -rf node_modules

Read the CONTRIBUTING.md file for instructions on how to best contribute to this repository.

Apache License, Version 2.0

© F5 Networks, Inc. 2023