Introduction

This code documentation provides a detailed step-by-step setup process to configure the poker game server along with the backend panel (Dashboard). Set your code just in a Few Hours!

Provided poker software contains a comprehensive backend code package that resides on a web server. The code architecture is designed on a modern microservice model to scale for millions of players. In code packages, there are four folders that are dedicated to unique services.

-Website Files -API Files -Game Server Files -Maintenance Server Files

Each folder can be configured on the dedicated instance to scale for higher traffic volume. This also increases the server cost, so it is recommended to plan your business need before code setup. For players up to 10,000, you can go with the single instance which is the most requested deployment process. URL Structure - Code Deployment We recommend you follow the subdomain-based structure during code deployment. It gives us a dynamic setup to connect from-end apps instead of IPs which is a static setup. Here are the sample sub-domains you must follow. A wildcard SSL is required if you go with multiple separate instance deployment methods.

(Admin Dashboard) dashboard.example.com

(Game API) connector.example.com

(Game Engine) gate.example.com

(Maintenance) maintenance.example.com

To increase security, the WebSocket connects only with SSL-enabled domains. For more details connect to the Pokerscript support team.