https://github.com/jcmcneal/react-step-wizard

Once the backend loses connection to the ts3 server once, it won't reconnect when it is back online.

The Index Page should contain information on the TS3 Channel Manager a tutorial

If a channel is not being used, the channel should be deleted after some time

• Store a timestamp in the database for ever channel: "inactiveSince"
• Every X minutes the Bot should check wether or not a channel is used (users online)
  • We can use cron for that (https://www.npmjs.com/package/cron)
• If a user is online, update the inactiveSince timestamp to current time
• If the inactiveSince timestamp is older than X days, the channel and DB Entry should be deleted
• If the channel is close to being deleted it needs to be tagged somehow
  • For example assign a Trash Icon as Channel Icon

• Currently a lot of functions are written using then/catch => Instead using async/await will look cleaner and more readable
• The Services (auth.service & channel.service) have bad error handling. This could be improved quite a lot
• Most Forms directly send a message to backend without validation. With local validation the server load can be reduced

• Follow DRY-Principle (currently there is some code repetition)
• Check if all HTTP Status Codes are correct
• Check if some async/ await functions can run in parallel (using Promises.all())
• Fix typos in response texts

The Login needs to consist of two different sub-pages

• The first one should contain a form to enter the ts uid.
  • It should also contain some information on how to find the ts uid.
• The second page needs a form to enter the validation code sent on teamspeak
  • After successful login: Forward to main-page
  • The JWT Auth Token also needs to be stored

• If a user is not authenticated he should not be able to visit /home and be redirected to /login
• If a user is authenticated and tries to visit /login he should automatically be redirected to /home

• Add Code Of Conduct
• Write Contributing Guidelines
• Add Issue Templates
• Add Pull Request Template

• This page should contain a web form with all necessary input fields to create a channel.
• After a successful creation: Forward to Internal Index Page

• Add some custom CSS
• Use Form Validation

• Show a list of channels created by the logged in user
  • The List should also contain edit and delete buttons

Using Docker and Docker Compose we can ensure that this project will run smooth on every environment. In addition it should also simplify the configuration for the admins.

The actual channel number needs to be calculated

• Channels numbers should be natural numbers (ascending)
  • Therefore: Find the first natural number that is not taken and assign it to the new channel
• After the number is calculated we can get the previous channel and choose it as a parent

The README should...

• give a brief introduction to this project,
• describe the features,
• give instructions on how to install.

If a user edits a channel the input fields are currently blank. It would be way more user-friendly to show the old values in the fields.

• The Backend needs the functions for Edit and Delete
  • Make sure that these functions can only be called be authenticated users
  • Users can only edit and delete their own channels
• The Frontend needs forms and functions to handle the operations