• Categories
  • Recent
  • Tags
  • Popular
  • Solved
  • Unsolved
  • Users
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Darkly)
  • No Skin
Collapse
brainCloud Forums

Quick iterative testing of Room Server lobbies locally [Unity][Mirror Networking]

Scheduled Pinned Locked Moved Solved General
4 Posts 2 Posters 177 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    PJ
    wrote on last edited by
    #1

    Hey! I'm in the middle of converting my Unity game to use brainCloud as a backend.

    I've followed this tutorial and am able to create a lobby and connect to the server. This is really cool, however, the fact that I need to build the Linux server binary, build the docker container, push the docker container, and (usually) wait for a server to warm up before the connection goes through, totally demolishes what was previously a fairly quick iteration time for testing the server.

    The tutorial I linked tells me to run the container locally. However, it also tells me I should just expect this to fail, since "we didn't pass-in environment variable". Is there a way to run the server in this container in such a way that I can use it to test the lobby functionality?

    Better yet, is there a good workflow that would allow me to reliably test the Lobby functionality of the server from within the editor? In addition to the pretty dire iteration time, viewing the logs on servers in Global -> Lobs -> Recent Errors (for which I had to override my Logger since it doesn't seem to pick up Unity's Debug.Logs by default) feels a bit cumbersome. Any tips, best practices, or links to docs I might have missed would be hugely appreciated!

    1 Reply Last reply
    0
  • Paul WinterhalderP Offline
    Paul WinterhalderP Offline
    Paul Winterhalder brainCloudAdmin
    wrote on last edited by
    #2

    Hi @PJ ,

    Have you seen our RoomServerDevTool? https://github.com/getbraincloud/braincloud-roomserver-devtool

    It allows you to setup your local workstation as a remote "Room Server" -- and then you can run and debug the server remotely. Basically brainCloud will attempt to launch a server to your workstation.

    Paul.

    1 Reply Last reply
    1
  • P Offline
    P Offline
    PJ
    wrote on last edited by PJ
    #3

    Thanks Paul. I hadn't encountered that before, but it looks like it will indeed be a huge help!

    I'm excited to give it a whirl, but while I have a few more hours before I can do so - Building to a docker container seems to be an important step in using this tool. Will I have any luck just running the server in the Editor and trying to point to my IP, or does some sort of magic happen in the docker container that truly makes it a critical step?

    Either way, this will make debugging much easier!

    EDIT: Will mark "Solved" either once you reply, or I'm able to verify this myself.

    1 Reply Last reply
    0
  • P Offline
    P Offline
    PJ
    wrote on last edited by
    #4

    Awesome! Still a few things to clean up but I appear to be right back to testing within the editor, but against brainCloud's actual lobby system. The key was setting debug to true in the config.js and following the instructions at the end of the GitHub page. Thanks again!

    1 Reply Last reply
    0
  • P PJ has marked this topic as solved on

  • Login

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Solved
  • Unsolved
  • Users