Launch Server Setup
The launch server is a server process that runs on linux that works in conjunction with the Launcher client application to verify the executable launched is the most current version. If the launcher application determines the launch server has a new version it downloads and installs the application from the launch server.
When do you need a Launch Server?
- By default, the HeroEngine team will configure your initial development world with a launch server so that you may easily receive updates to both server and client applications during the development process.
- If you are configuring your own world, we recommend the use of a launch server but you could utilize a different distribution method if you choose.
When do you not need a Launch Server?
- If you have an alternate method of distributing new client and server applications then you may not need a launch server.
- If you do not plan to use the Launcher application
- You already have one running (i.e. you do not need to create a launch server for each world)
The initial installation of the Launch Server will generally be handled by the HeroEngine team. A local webpage will also be established with your world-specific downloads, and a Launcher client which will assist with the rest of the installation process.
- Operating System Installation: CentOS 5.3
- Install and configure Apache
Create Groups and Users
The launcher server requires the heroengine group/user exists.
useradd -g heroengine -d /opt/heroengine -m -s /bin/bash heroengine
Files needed for the Launch Server
launchserver - Launch Server Executable
launchserver.cfg - Launch Server Config file, used to specify the port to listen on
startlaunchserver - Script to start Launch Server and cronolog
clients.cfg - Config file that specifies products' version numbers and installation files
Start - Calls the starthelaunchserver script
cronolog - Logging utility. Logs are placed in the logs subdirectory
lnchinst.exe - The installer for your Company-Specific client launcher