Replies: 1 comment
-
This Dockerfile creates a HTTP server that handles requests at DeploymentThe docker application is intended to be deployed as a web service that is separate from your game server. Game servers deployed as HTTP hosts run into the same issue that the repository MultiplayerServerSecureWebsocket mentions as a problem for games hosted on a https domain - you can't generate a SSL certificate for the fully qualified azure.com domain name of each server session. Azure App Service is an "off the shelf" solution for the docker application. Linux and Windows should be supported since .NET Core is cross platform. Integrating with your web clientWhen your web client configures a web socket connection i.e. ConnectEndpoint with Unity or WebSocket in client side JavaScript, you'll use the fully qualified domain name from your deployed web service. For example, if you created an Azure App Service, the full qualified domain name would be something like |
Beta Was this translation helpful? Give feedback.
-
I'm not really good with network side of things. So, as far as I can assume, I'll just build this as a docker and run it on the server ? Then run the server docker build ( with a configured simple web transport) ? Or maybe should I combine this dockerfile with the one I created for the server build ? Sorry for my terrible understanding (if any.)
(:
Beta Was this translation helpful? Give feedback.
All reactions