create new server management pages

[McMelonTV]

We want to replace the original server management page made only for the demo with a new one. This page should include some kind of tabs which would let you see different subpages for the different parts of server management.

The subpages should include:

• Console
  • shows the server console and a command line for the user to run commands
  • has a way to switch between the server console (software/service output) and the server's actual docker container terminal (os)
  • has power action buttons
  • shows basic server resource usage statistics
  • shows basic server info like it's name, uptime, software and ip:port
• Stats
  • shows more advanced server statistics including resource usage, network usage,....
• File Management
  • has a file browser and editor
  • shows the user's sftp access details for the server
• Networking
  • lets the user assign additional ports to the server
• Settings
  • lets the user change the server's name, software, and potentially the start command

[Viliam-Grinc]

From what I understand, the page should be structured like this:

• /[id]: Basically a layout holding subpages as tabs
• • /console: A console page you described
• • /stats: Advanced statistis as you described
• • /file-manager: As we discussed, we should use some library for this. Should I look for it, or you will do the research?
• • /networking: Using multiple ports and working with them as you described
• • /settings: Changing main server attributes

Question:

What is part of the issue? Is it building layout? Is it building layout and placeholders for now? Or is it building everything?

For me, it would be best if I build layout with placeholders, and than with each additional feature create a new branch work on it and push it. Create, work, and push. But ofc I will do what is wanted from me.

[McMelonTV]

This issue is for everything, I will create sub-issues for the layout itself as well as the sub-pages. You can work on it in whatever order you'd like, though the layout should probably be done first. The actual structure of this should be as follows:

• /server/[id] - React Router prefix, has the layout for the tabs
  • /console
  • /stats
  • /files
  • /network - this might also be used for setting up firewall rules and stuff like (sub)domains in the future
  • /settings

As for the actual content of the sub-pages I can send you more details or draw a sketch if needed. For the file manager, I have to do a bit more thinking on how to actually implement it on the backend and then figure out what the best way to make the frontend for it would be, so you don't have to bother with that just yet.