Ensure input test implementation is aligned to current input API.

Use path relative to server executable instead of current working
directory.

Make server use standard output streams instead of file-based streams.

Add capability to log outside stderr and stdout.

Use abstraction instead of using SDL dependencies.

Ensure game/server configs sit in game directory for easy editing and referencing.

The logging for the network teardown has been put in the appropriate function.

Use CMake definitions to specify config paths and filenames.

Come up with our own logging system.

Include _s wrappers for most standard function calls.

Ensure every config-backed subsystem can serialize/deserialize config in
a single consistent manner.

Add templates for config item types.

Also updated server's config to use the global config module.

Remove symlinks and make codebase use common modules instead.

Rename files in order to prepare for extraction for publishing
subsystems independently.

Unify config loading in net and video subsystems.

Make sure to have help messages for both the game and the server.

Ensure no side effect persists when errors have been triggered.

Database will be used for authentication.

Update documentation.

Implement the sending of input events to the websocket server.

Update identifiers to be consistent.

Add subdirectories for grouping net-related functions.

Make server optionally have a mountpoint for putting assets.

Point symlinks to relative paths.

Copy implementation from lws.

Connect client to server, save connection details.

Ensure the same reference of the server is terminated in the server,
while the client should check the context when connecting/disconnecting.

Attempt to connect client to server.

Ensure mounts are configurable.

Isolate network logic to each subsystem.

Split callback logic into several functions.

Update initialization method.

Use ring example.

Use minimal server echo example instead.

The client app is able to connect to the server, however no further
communication is happening. Must've been the callbacks?

Also the client app enters into an infinite loop when lws_service() is
called inside the game loop.

Add libwebsockets client to game executable.

Protocol retrieved from lws git repo for samples.

Websockets server is for game networking.