Security
This project does not explicitly implement security measures. This includes authentication, authorization, or data encryption.
The project relies on the Firebase database to store data. Firebase has its own security rules, which are implemented in database.rules.json
. These rules govern access to data based on user authentication.
The project makes use of Firebase authentication, which is not explicitly covered in the documentation.
To review security rules:
audience-app/database.rules.json
The following code snippets from audience-app/public/assets/main.js
indicate that the project stores user data in local storage:
tryGet(key)
trySet(key, value)
For information about the use of Firebase authentication and the storage of user data in local storage:
Top-Level Directory Explanations
audience-app/ - This directory contains the files for the audience-facing part of the application. It includes HTML files for different pages, static assets like images, and configuration files for Firebase and npm.
audience-app/public/ - This subdirectory holds the publicly accessible files of the audience app. It includes HTML files for specific pages, images, and other static assets.
presenter-app/ - This directory contains the files for the presenter-facing part of the application. It includes source code, static assets, and configuration files.
presenter-app/build/ - This subdirectory holds the compiled and bundled files for the presenter app. It includes HTML, CSS, JavaScript, and image files.
presenter-app/src/ - This subdirectory contains the source code for the presenter app. It includes components, controllers, routes, styles, and utility functions.
presenter-app/tests/ - This subdirectory contains test files for the presenter app. It includes mocks, controllers, and declarations.