Some Scoping for MVP

[mathematicalmichael]

Nice to Haves

• specify version (this is complicated by backups / restores, need to be version-aware)
• allow for ftp connection to server so that the admin (person deploying the service) can actually make themselves an admin and install various mods.
• allow the admin to send an arbitrary docker exec command from the frontend (login protected so only admin can do it)
  • THIS REQUIRES USER TIERS
    • user tiers
    • superuser
    • regular users (start/stop)
    • viewers (see IP)
  • do we use an admin panel to allow them to interact with the minecraft shell, restart minecraft server (without rebooting EC2)
• BILLING.
  • collect payment from your users

Must Haves

• documentation for how to set up the server.

  • "I've never used AWS. How do I set up an account and get the relevant credentials?"
  • full deployment walk-through, how to get all the dependencies (WOULD BE NICE TO ONLY NEED DOCKER, but MVP will be okay with clear docs on "install node, docker, aws-cdk installed with npm -g")
  • how does that person get admin access to themselves?

• MVP workflow:

  • document how to get to AWS Console for EC2 and what docker exec commands to issue to accomplish command setup tasks.
  • FTP access, so document how to add their ssh key and go about uploading config files.
  • rebooting the EC2 (issue destroy, deploy) will be how they restart the mc server for changes to take effect.

• How will the admin "add their friends" to be able to log in to the frontend and start/stop the server.

  • cognito console where they can make users and groups
    • we will add groups ourselves (to the stack) and tell the admin to only add their friends to these groups

• the person starting the server can provide their username to become "admin by default" (no need for Console access)

  • the user_data script will have to wait for the minecraft server to start up (finish downloading its jar file) then issue the admin granting command.

[mathematicalmichael]

post MVP: will be really nice to have a "migration workflow" (how do I as a user move my existing server over to this new deployment?)