113ad3d917
App Translocation makes it nearly impossible to find the interface executable from the running server-console, specifically in downloaded builds launched from the Finder. To enable OSX detection and and launch of the interface, the code has been changed to: * Assume interface is installed on OSX as we don't produce a server-only build. * Launch the interface by using 'open' with the appid. NOTE: This may launch the wrong version of the app if multiple instances of the app are installed, but this is the best we can do for now. For most users, the behavior should be as expected. Second, polling was happening even if interface couldn't be detected if it was previously enabled. |
||
|---|---|---|
| .. | ||
| resources | ||
| src | ||
| .gitignore | ||
| CMakeLists.txt | ||
| package-lock.json | ||
| package.json | ||
| packager.js | ||
| 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.