Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replays should know what server they're available at #3

Open
7 tasks
allejo opened this issue Jun 24, 2019 · 0 comments
Open
7 tasks

Replays should know what server they're available at #3

allejo opened this issue Jun 24, 2019 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Milestone

Comments

@allejo
Copy link
Owner

allejo commented Jun 24, 2019

Replay entities should know what bzfs server they are available at.

  • A new Server entity should be created and have the Replay entity as a foreign key. This way, if the server moves or changes addresses, it only has to be updated in one location. This entity should have the following fields
    • Hostname
    • Port (what port is the replay server located at, NOT what server did this match take place on)
    • Owner (a user's BZID, make this an int for now)
  • Add new commands to support the following:
    • Creating a new Server instance and have a walk through of inputting information
    • Modify app:replay:import and add a new CLI flag that lets you specify a Server ID; e.g. --replay-server
@allejo allejo added enhancement New feature or request help wanted Extra attention is needed labels Jun 24, 2019
@allejo allejo added the good first issue Good for newcomers label Jun 24, 2019
@allejo allejo added this to the 1.0.0 milestone Jun 27, 2019
@allejo allejo mentioned this issue Sep 8, 2019
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant