gerazo/eltelive

eltelive's Issues

Installation - Clarification for mongoDB

It might be that I'm not that experienced with mongoDB, and a more advanced user wouldn't have this issue, but it's not exactly clear which type of deployment/version do I need, because their website is confusing. apt-get install mongodb did work on ubuntu though.
Again, it might be that I'm simply just too stupid to figure out how to install it from the site.

Chat: One time interaction

Temporary chat per session

Enhancement: Copy generated key on select/click (Copy to clipboard)

After Key is generated there must be a button or functionality to copy the key easily /automatically
following key examples are not easy to select (double click )
b7w56-1rO
e1-rGnpug

Generate key button @click renders Login Page again (Only Firefox )

Specific Scenario

{{url}}/#/login -> Log in Successfully -> {{url}}/#/active-stream -> click to Generate Key -> Renders Login Page again (/#/login )

Tested Browser Results :
Firefox 92.0 & 93.0 ✗
EDGE 94 ✓
CHROME 94 ✓

Chatbox-Design

Design Chatbox UI/UX
https://github.com/gerazo/eltelive/projects/1#card-66338643

Installation - creating the .env file is ambigious

The location of the .env file that the user has to create is not specified, and can be confusing. It worked for me first try, but specifying the folder to create the file in could clarify it. Alternatively a pre-generated empty .env file could be used as well.

Chat: Design

Implement a design for attendees (students) chat for temporary interaction. This chat should be deleted after session.

health statistics and streaming feedback

feedback will show the statistics of the lecture: How many
participants are there, how much bandwidth is used compare to standard. And also we need
"health" statistics about the actual stream: is the streaming working,
what is the load of the CPU, memory, are there dropped images... Behind
this, the idea that the presenter should get a feedback about whether
the server receives his/her stream correctly.
Imagine that a student comlains: I can't hear anything, or the sound is
crappy. Is it the presenter's net or computer? Is it the server's
problems? Is it the student's net?
So such a feedback can help anyone
in this process.

Frontend variables are still undefined even after the .env file works properly with the other uses

I have managed to set up the .env file, so that it can read the variables for the mongodb connection properly (see #9 ), however even after I have tested and found that the DB is running properly, the frontend variables still resolve as undefined.

Uncaught (in promise) TypeError: Window.fetch: http://undefined:undefined/api/register is not a valid URL. _callee$ sign-up.vue:107

after checking the code, they use the variables process.env.VUE_APP_HOST and process.env.VUE_APP_NODE_JS_PORT, which are in the .env file.

CLI commands clarity

The build and the lint commands are lacking in explanation (when should one exactly use them? an example might help)

Overlay for guest/streamer guide breaks if alt-tabbed and waiting long enough

Sometimes (I can't exactly reproduce the issue) when I alt-tabbed and was exploring some code while having a guide open, the box itself with the text disappeared while the gray overlay stayed without me having any way to close it.

Cannot connect to the db

the page does not react to the register or to the login buttons, the server part also gets the following error message:
server running on port 4000
(node:34021) UnhandledPromiseRejectionWarning: MongooseError: The uri parameter to openUri() must be a string, got "undefined". Make sure the first parameter to mongoose.connect() or mongoose.createConnection() is a string.
at NativeConnection.Connection.openUri (/home/x/Desktop/eltelive/eltelive-new/node_modules/mongoose/lib/connection.js:694:11)
at /home/x/Desktop/eltelive/eltelive-new/node_modules/mongoose/lib/index.js:351:10
at /home/x/Desktop/eltelive/eltelive-new/node_modules/mongoose/lib/helpers/promiseOrCallback.js:31:5
at new Promise ()
at promiseOrCallback (/home/x/Desktop/eltelive/eltelive-new/node_modules/mongoose/lib/helpers/promiseOrCallback.js:30:10)
at Mongoose._promiseOrCallback (/home/x/Desktop/eltelive/eltelive-new/node_modules/mongoose/lib/index.js:1149:10)
at Mongoose.connect (/home/x/Desktop/eltelive/eltelive-new/node_modules/mongoose/lib/index.js:350:20)
at Object. (/home/x/Desktop/eltelive/eltelive-new/db_connections/db.js:6:10)
at Module._compile (internal/modules/cjs/loader.js:1185:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1205:10)
at Module.load (internal/modules/cjs/loader.js:1034:32)
at Function.Module._load (internal/modules/cjs/loader.js:923:14)
at Module.require (internal/modules/cjs/loader.js:1074:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object. (/home/x/Desktop/eltelive/eltelive-new/server.js:11:18)
at Module._compile (internal/modules/cjs/loader.js:1185:30)
(Use node --trace-warnings ... to show where the warning was created)
(node:34021) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:34021) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Ubuntu 20.04.3