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

EPIC: Create a server for a multiplayer support #39

Closed
23 tasks done
Dominux opened this issue Dec 29, 2022 · 4 comments
Closed
23 tasks done

EPIC: Create a server for a multiplayer support #39

Dominux opened this issue Dec 29, 2022 · 4 comments
Assignees
Labels
enhancement New feature or request server

Comments

@Dominux
Copy link
Owner

Dominux commented Dec 29, 2022

  • Пользователь создает аккаунт
  • Пользователь создает комнату
  • Пользователь может получить комнату по ссылке
  • Пользователь создает ссылку на приглашение в комнату
  • Пользователь принимает ссылку на приглашение в комнату и добавляется в нее как второй игрок
  • Первый игрок начинает игру
  • Открыть WS соединение
  • При создании игры создавать историю
  • Создать сущность записи истории
  • Делать новые записи каждый ход
  • При отмене хода - удалять запись
  • Добавить страницу выбора режима игры, синглплеер будет везти к существующей версии игры, мультиплеер - к новой, серверной
  • Запустить бэк в дев режиме
  • Подключить к бэку фронт
  • Добавить страницу регистрации
  • Добавить страницу комнат с возможностью ее создания
  • Добавить страницу комнаты по id, с видом, кто из игроков уже есть и кнопкой начала игры у черного (первого) игрока
  • Удалять room states когда оба игрока отключились от сокета
  • Зарезолвить баг с роутингом фронта на проде
  • Баг в синглплейре - камни ставятся, начиная с белого, а не с черного
  • Разворачивать бэк на сервере
  • Бэк по HTTPS
  • Проксировать трафик wss
@Dominux Dominux added enhancement New feature or request server labels Dec 29, 2022
@Dominux Dominux self-assigned this Dec 29, 2022
Dominux added a commit that referenced this issue Dec 29, 2022
@Dominux
Copy link
Owner Author

Dominux commented Dec 29, 2022

image

Dominux added a commit that referenced this issue Dec 29, 2022
Dominux added a commit that referenced this issue Dec 31, 2022
Dominux added a commit that referenced this issue Jan 2, 2023
Dominux added a commit that referenced this issue Jan 2, 2023
Dominux added a commit that referenced this issue Jan 2, 2023
Dominux added a commit that referenced this issue Jan 2, 2023
Dominux added a commit that referenced this issue Jan 3, 2023
Dominux added a commit that referenced this issue Jan 3, 2023
Dominux added a commit that referenced this issue Jan 3, 2023
Dominux added a commit that referenced this issue Jan 4, 2023
Dominux added a commit that referenced this issue Jan 4, 2023
Dominux added a commit that referenced this issue Jan 4, 2023
Dominux added a commit that referenced this issue Jan 6, 2023
Dominux added a commit that referenced this issue Jan 6, 2023
Dominux added a commit that referenced this issue Jan 8, 2023
Dominux added a commit that referenced this issue Jan 8, 2023
Dominux added a commit that referenced this issue Jan 8, 2023
Dominux added a commit that referenced this issue Jan 9, 2023
Dominux added a commit that referenced this issue Jan 9, 2023
@Dominux Dominux pinned this issue Jan 10, 2023
Dominux added a commit that referenced this issue Jan 17, 2023
Dominux added a commit that referenced this issue Jan 17, 2023
Dominux added a commit that referenced this issue Jan 17, 2023
Dominux added a commit that referenced this issue Jan 17, 2023
Dominux added a commit that referenced this issue Jan 17, 2023
Dominux added a commit that referenced this issue Jan 17, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
@Dominux
Copy link
Owner Author

Dominux commented Jan 18, 2023

Dev contains that
2023-01-18T16:57:53.706417Z INFO request: finished processing request latency=0 ms status=101 method=GET uri=/games/ws/e089bfdb-3de1-4224-988e-ebd3bb464033 version=HTTP/1.1
Prod doesn't

@Dominux
Copy link
Owner Author

Dominux commented Jan 18, 2023

PROD does:
2023-01-18T17:41:09.690924Z INFO request: finished processing request latency=0 ms status=400 method=GET uri=/games/ws/32d3eb14-9219-448e-b7dc-c33bab85e65c version=HTTP/1.0

@Dominux
Copy link
Owner Author

Dominux commented Jan 18, 2023

It works on the simple chat example placed in same conditions (machine, docker container, nginx conf and domain/subdomain)
So it seems like that 400 error is really cause of wrong request or something like that

Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
Dominux added a commit that referenced this issue Jan 18, 2023
@Dominux Dominux closed this as completed Jan 18, 2023
@Dominux Dominux unpinned this issue Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request server
Projects
None yet
Development

No branches or pull requests

1 participant