Skip to content

1. RUNNING IN DEVELOPMENT MODE

  • Clone this repo.

  • Learn your host machine's LAN IP address:

$ ifconfig | grep -Eo 'inet (addr:)?([0-9]*\.){3}[0-9]*' | grep -Eo '([0-9]*\.){3}[0-9]*' | grep -v '127.0.0.1'

192.168.***.***

  • Open backend/config.yml file, write your LAN IP address into server/udp/dockerHostIp section.

  • If you don't have VS Code and Remote Development extension pack installed, install them. This link can be helpful.

  • Start VS Code, open the cloned folder of "webrtc-nuts-and-bolts".

  • Press F1 and select "Remote Containers: Open Folder in Container..." then select "backend" folder in "webrtc-nuts-and-bolts".

Open folder in container

Select "backend" folder

  • This command creates (if don't exist) required containers in Docker, then connects inside of webrtcnb-backend container for development and debugging purposes.

  • You will see this notification while building image and starting container. If you click on this notification, you will see a log similar to image below.

Starting Dev Container small

Starting Dev Container log

  • When webrtcnb-backend container has been built and started, VS Code will ask you for some required installations related to Go language, click "Install All" for these prompts.

Install Go Dependencies small

  • After clicking "Install All", you will see installation logs similar to image below.

Install Go Dependencies log

  • When you see "You are ready to Go. :)" message in the log, you can press F5 to run and debug our server inside the container. VS Code can ask for installing other dependencies (like "dlv"), click on "Install" again. If VS Code asked for some extra installations, after installation you may need to press F5 again.

  • You can switch to "DEBUG CONSOLE" tab at bottom, you will be able to see the output of running server application:

Backend initial output

  • Now your backend server is ready to accept requests from browser!