Shulou(Shulou.com)06/01 Report--

This article mainly introduces "how to transform gbc into windows version". In daily operation, I believe many people have doubts about how to transform gbc into windows version. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubts about "how to transform gbc into windows version". Next, please follow the editor to study!

The characteristics of gbc VS kbe: traditional server cluster and component server system

This comparison is almost the difference between specialized server clusters (traditional servers) and scripted components (component servers) that vs logically clears.

It has a domain protocol processing system composed of beanstalked and pbc. Niginx is only responsible for io and transit. I think this is in addition to the logical processing of the back end of the language, its network protocol processing is another major feature of component serverization, which uses the language as a container to make worker. Each script is an app, a feature of an application, and two major efforts that can be used for both a game server and a general HTTP WEB server.

It can be seen that the logic of the component server is clearer, highlighting the language back-end, CS/BS all-package architecture, and the ability to customize the logic engine. Compared with PAAS in single language environment, it can be connected with multiple languages to promote PAAS in multi language environment at the same time.

Gbc is transformed into windows version

Gbc is only released and run in Unix by default, and the process logic is basically that py virtualenv uses supervisor to start the guardian process of nginx,redis,beanstalk+2 app: since openresty and other components as the main body are implemented on windows, it can be easily transplanted to windows except that supervisor cannot be colonized under win. There is only that supervisor in the whole process, as long as you remove this (and replace it with a normal windows-supported call method), the framework and package of gbc itself do not need to be moved.

Changes: mainly the configuration part and startup part (there are four files start_server,shell_func.sh,shell_func.lua,start_work.lua that need to be involved and simplified, the first two can be deleted directly. I made it into the following simplified and condensed bat as follows), and the last two files need to be greatly changed (see download for parts that involve a lot of path modifications):

Luajit% CD%\ update_config.luacd% APPSTACK_ROOT%\ openresty\ RunHiddenConsole nginx2cd% APPS_ROOT%\ gbcdata\ RunHiddenConsole beanstalkd-l 127.0.0.1-p 11300-b% APPS_ROOT%\ gbcdata\ dbRunHiddenConsole redis-server2% APPSTACK_ROOT%\ redis\ redis.confcd% GBC_ROOT%\ REM the path here should be in the form of configs for key in workerbootstrape: where local appConfig = self._ configs [appRootPath] start luajit start_worker.lua% APPSTACK_ ROOT%\ gbc% APPS_ROOT:\ = /% / gbcdata/apps/welcomestart luajit start_worker.lua% APPSTACK_ROOT%\ gbc% APPS_ROOT:\ = /% / gbcdata/apps/tests here The study on "how to transform gbc into windows version" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.