Mirrors/overte
3
0
Fork 0
mirror of https://github.com/overte-org/overte.git synced 2025-04-08 12:52:45 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
overte/server-console
History
Ryan Huffman 36d725b67a Update content downloader to always d/l if no content present
2016-01-20 15:51:08 -08:00
..
resources rename console directory to server-console 2016-01-19 16:11:08 -08:00
src Update content downloader to always d/l if no content present 2016-01-20 15:51:08 -08:00
.gitignore rename console directory to server-console 2016-01-19 16:11:08 -08:00
CMakeLists.txt rename the console targets to server-console 2016-01-19 16:15:01 -08:00
package.json add migration for stack manager content 2016-01-20 14:40:12 -08:00
packager.js rename console directory to server-console 2016-01-19 16:11:08 -08:00
README.md more tweaks to server console readme 2016-01-20 11:27:29 -08:00

README.md

Console

The High Fidelity Server Console, made with Electron.

Running Locally

Make sure you have Node.js installed. Use the latest stable version.

npm install
npm start

To run, the console needs to find a build of Interface, domain-server, and assignment-client.

The command npm start tells the console to look for builds of those binaries in a build folder beside this console folder.

On platforms with separate build folders for release and debug libraries npm start will choose the debug binaries. On those platforms if you prefer to use local release builds you'll want npm run local-release.

Packaging

CMake produces a target packaged-server-console that will bundle up everything you need for the Server Console on your platform. It ensures that there are available builds for the domain-server and assignment-client. Then it produces an executable for the Server Console.

The install target will copy all of the produced executables to a directory, ready for testing or packaging for deployment.