overte-AleziaKurdis/server-console
Marcus Llewellyn 96047d7536 Attempt find/replace all "High Fidleity" strings with "Vircadia"
Also updates most URLs to point to Vircadia resources with the exception of the serverless domain tutorial.

Branched from `v0.86.0-k2`
2020-03-31 14:33:08 -05:00
..
resources - updated console+server icons, installer+uninstaller graphics, and console notification icon 2019-04-26 14:50:18 -07:00
src Attempt find/replace all "High Fidleity" strings with "Vircadia" 2020-03-31 14:33:08 -05:00
.gitignore changes to electron app for Sandbox rename 2016-03-30 12:41:13 -07:00
CMakeLists.txt More CR Fixes 2018-10-04 15:36:31 -07:00
package.json Attempt find/replace all "High Fidleity" strings with "Vircadia" 2020-03-31 14:33:08 -05:00
packager.js Attempt find/replace all "High Fidleity" strings with "Vircadia" 2020-03-31 14:33:08 -05:00
README.md more tweaks to server console readme 2016-01-20 11:27:29 -08:00

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.