When starting the Restreamer-UI container and opening the GUI, i need to change the admin credentials of the Restreamer-Core. These credentials are already set while booting the core(docker-compose file).

Changing the credentials in the Restreamer-UI allows the ui to proceed to the login prompt. In this login prompt the newly "changed" credentials are not working. The Restreamer-Core credentials as specified on boot do still work.

Maybe try to make a toggle, or change the way the UI connects to the core to bypass the creation of a (non-working) admin user.

Reduce the size of the Docker image by only holding the production build of the UI. The files are served by Caddy server. For bundling, the production build files are still in /ui/build

While running Restreamer-UI i have noticed the process taking up upto 100% cpu and 2gigs of memory (just the UI). while using the composefile below:

When adding mem_limit: 500m and cpus:0.50, the ui wont even start anymore. indicating something might be wrong with the ui (process node /ui/node_modules/react-scripts/start.js is running at max cpu). 500Megabyte of memory and 1.5Ghz should be plenty to run a basic gui under normal circumstances.

Also the documentation lacks explanaition about the current state of restreamer-ui and the posibility to connect to the core at the correct methods.

docker logs output:

> react-scripts start

ℹ ｢wds｣: Project is running at http://172.20.0.3/
ℹ ｢wds｣: webpack output is served from 
ℹ ｢wds｣: Content not from webpack is served from /ui/public
ℹ ｢wds｣: 404s will fallback to /
Starting the development server...

The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process.
npm WARN config cache-min This option has been deprecated in favor of `--prefer-offline`.

docker-compose.yml:

services:
  restreamer:
    image: datarhei/core:latest
    container_name: restreamer
    restart: always
    ports:
      - 8080:8080
      - 1935:1935
    volumes:
      - /opt/datarhei/data/core/config:/core/config
      - /opt/datarhei/data/core/data:/core/data
    environment:
      - CORE_API_AUTH_USERNAME=${API_USERNAME}
      - CORE_API_AUTH_PASSWORD=${API_PASSWORD}
      - CORE_RTMP_ENABLE=true
      - CORE_RTMP_ADDRESS=:1935
      - CORE_RTMP_APP=/live
      - CORE_METRICS_ENABLE=true
      - CORE_METRICS_ENABLE_PROMETHEUS=true
  restreamer-gui:
    image: datarhei/restreamer-ui:latest
    container_name: restreamer-gui
    restart: always
    depends_on:
      - restreamer
    ports:
      - 3000:3000```

Snyk has created this PR to upgrade @mui/styles from 5.6.2 to 5.7.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

• The recommended version is 1 version ahead of your current version.
• The recommended version was released 21 days ago, on 2022-05-10.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade @auth0/auth0-spa-js from 1.21.0 to 1.21.1.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

• The recommended version is 1 version ahead of your current version.
• The recommended version was released 21 days ago, on 2022-05-10.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade @mui/material from 5.6.3 to 5.7.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

• The recommended version is 2 versions ahead of your current version.
• The recommended version was released 21 days ago, on 2022-05-10.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade video.js from 7.18.1 to 7.19.2.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

• The recommended version is 3 versions ahead of your current version.
• The recommended version was released a month ago, on 2022-04-20.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade hls.js from 0.13.2 to 0.14.17.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

• The recommended version is 312 versions ahead of your current version.
• The recommended version was released a year ago, on 2020-12-09.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Would it be a sensible roadmap item to have UI able to manage multiple instances of Core?

I'm currently experimenting with Restreamer in a context where we have 4x boxes with AJA capture cards handling a few channels of encoding each (Currently gstreamer, but we'd like to switch to something a bit more orchestratable).

As it is, we're running the bundled docker container on each box, but this does require running 4x tabs of UI for managing the four boxes.

It would be nice to be able to point a UI instance at multiple instances of core, and manage all 12 streams from one UI.

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json
  • yarn.lock

Vulnerabilities that will be fixed

With an upgrade:

Severity | Priority Score (*) | Issue | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:------------------------- | 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5 | Prototype Pollution
SNYK-JS-LOADERUTILS-3043105 | Yes | No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information: 🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution

Restreamer has a url to get player configs: https://[restreamer-domain]/channels/[GUID]/config.js

this returns the following script file (example): var playerConfig = {"autoplay":false,"mute":true, ... }}

I think it would be better to just return the json part, without "var playerConfig = ", that way it would be much more interoperable, without needing to instantiate script to get a var name, that is more hardcoded.

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json
  • yarn.lock

Vulnerabilities that will be fixed

With an upgrade:

Severity | Priority Score (*) | Issue | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:------------------------- | 551/1000
Why? Recently disclosed, Has a fix available, CVSS 5.3 | Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-3050818 | Yes | No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information: 🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

Hello!

It'd be nice to see a resolution option, like with bitrate where you have few ready ones and a possibility for custom one. Additionally, "Expert-mode" text-input box where you can specify FFMPEG filters yourself.

Keep up the good work!