Installation

Introduction

These are slightly more in depth installation instructions. Before beginning the installation instructions, I would assume you have set up the following:

• Exchange Online (Office 365)
• Conference room mailboxes organized in room lists
• Exchange Web Services (EWS) enabled
• A service account with access to all conference room mailboxes and EWS
• A server to be used as a web server to host the application

---

General Installation

1. Install Node.js on your server. This will give you the two terminal commands node and npm.
   • Optional: If you are working on a Windows Server without IIS, I like to install cmder as a console emulator.
2. To ensure Node has installed correctly, you can type node -v and npm -v in your desired console (cmd, terminal, cmder, etc.). It should return a version number to the console.
3. Clone the repository or download the Zip file and unpackage it where you want the files to be served from.
4. In your console, navigate to the root directory of the repository, where the server.js and package.json files are located.
   • The package.json file manages all of the dependencies for the application.
5. In your console at the root directory, type npm install. This command will tell Node Package Manager (npm) to download and install all of the app's dependencies.
6. In your console, navigate to the ui-react/ folder. This folder contains all of the source files for the React.js front end.
7. Type npm install here as well. This will download and install all of the dependencies for the React.js front end.
   • By default, this app will run on port 8080. If you would like to change the port, you'll have to change it in three locations:
   • server.js
   • ui-react/package.json
   • ui-react/src/config/flightboard.config.js
8. Once you have your port configured the way you want it, in your console, navigate to ui-react/ and type npm run build. This will create your production ready files from your React.js source.
9. Finally, in your console, navigate back to the root of the app and run node server.js to serve your app.
   • In a production environment, you'd want to use a package like node-forever to ensure your server runs continuously.

IIS

Coming soon