Write cache micro service in es6.

• Rest API endpoint to set data in cache
• Rest API endpoint to get a specific session from cache
• Rest API endpoint to pull all sessions from cache

When you click on a given user, make sure you only see the convo relevant to that person

To container the app, we will need:
Check the README.md file for how to pull and use the redis and keycloak containers.

• Dockerfile for the frontend
• Dockerfile for the cache service
• docker-compose.yml file to start the
  - Redis Container
  - keycloak server container
  - frontend
  - redis micro-service

Upon loading the dashboard container all cookies should have saved and stored in local storage.

• AUTH_SESSION_ID
• KEYCLOAK_IDENTITY
• KEYCLOAK_SESSION

Clean up the cache system and remove the sessions from the cache as soon as users logout.

Spawn two websocket events for LOGIN and LOGOUT and adjust the cache when the state of the concurrent users changes.

Second: Write a Cache Subscriber, that is subscribed to the state of the cache and will notify and change the cache automatically upon changes.

write a component in the top nav bar for uploading user images. The component should be a modal where the user can add attributes to their user.

There is an endpoint in the Cache app that allows you to point out remove images and the node service downloads the resources. They will be in the public directory of the cache site and the names need to be intuitive so they will be easy to pull during the login process.

The image will sit in the top nav bar and there will be a component for editing and changing images.

The chat bubbles sometimes render without the text inside.

To provider more detail. When you have the app running and all the latest code pulled, you will notice the very first Chat send renders in a small circle without text.

I have trimmed the message of null and whitespace already.

Upon being redirect tp DashboardContainer, call the cache endpoint to get all sessions.

• call all sessions endpoint
• Populate left panel with current usernames

Explain implementation methodologies for easier contribution from the community.

Markdown file explaining the resources are tools required to spin up the resources.

Created a landing page that does not require authentication.

Requirements

• Incorporates the theme changer but in minimal form, like the other components, no drastic changes in theme.
• Has animations that are triggered by during non-active times.
• Has a button for signing back on.

Take user info from keycloak object and store into the UserReducer.

• realmAccess roles
• resourceAccess account roles
• token
• idToken
• refreshToken
• idTokenParsed- email
• idTokenParsed- name
• idTokenParsed- preferred_username
• idTokenParsed- given_name
• idTokenParsed- family_name