Table of Contents

• Getting Started
• Running the app in Docker
• Know issues in the application

Getting Started

Clone the repository to your machine:

$ git clone https://github.com/jj-stigell/fs19_full_stack_app.git

Running the app in Docker

You can use docker to run the whole app (database, frontend, and backend) in containers. Use the following command to run the app:

$ docker compose up

The app will be available at http://localhost:3000

You can login to app with test account (owner in the provided organization):

email: eddy.example@gmail.com
password: #MySuperS3cretP4ssword#

You with normal user (not owner of the provided organization):

email: normal.user@gmail.com
password: #MySuperS3cretP4ssword#

Note. If you want the email service (registering user, forgot password, invite user, etc.) to work in the demo, you must export or setup your own environment variables in the docker-compose.yaml file for:

SPRING_MAIL_USERNAME: example@email.com
SPRING_MAIL_PASSWORD: xxxx yyyy zzzz wwww

Backend API documentation is available at http://localhost:10000/swagger-ui/index.html

Known Issues in the Application

• Deleting a resource does not work if the backend's delete cascade is not functioning properly. No workaround was implemented during the frontend project.
• Optimistic updates require further refinement.
• Some endpoints require a manual page refresh to display updates (e.g., deleting a workspace user is not immediately reflected in the UI).
• Certain queries invalidate tags and cause the entire page to rerender, instead of updating the cache and rerendering only the affected parts.
• The notifications component currently uses mock data; neither the frontend nor the backend has notifications fully implemented.