-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathapp.js
More file actions
121 lines (101 loc) · 3.37 KB
/
app.js
File metadata and controls
121 lines (101 loc) · 3.37 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
/**
* This is file where the express application is started. Express is a
* "Fast, unopinionated, minimalist web framework for Node.js"
* (https://expressjs.com).
*
* In here we couple the Multiscreen Application to either the HTTP or
* websocket, and configure the HTTP/Websocket server. The actual
* initialization of the server is done in /bin/www
*
* The routes (how a specific requrest to URL is handled) are configured in
* routes/index.js
*
* We use handlebars (extension of mustache) as the templating engine.
*/
var express = require('express');
var path = require('path');
var favicon = require('serve-favicon');
var logger = require('morgan');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser');
var exphbs = require('express-handlebars');
var MSTApp = require('./multiscreen/mst-app.js');
var MSTHttpInterface = require('./multiscreen/mst-http-interface');
var MSTSocketInterface = require('./multiscreen/mst-socket-interface');
var routes = require('./routes/index');
var users = require('./routes/user');
var app = express();
//This is where the Multiscreen App is initialized
var mstApp = MSTApp();
//This is where we attach the websocket handler to the Express app
var socketIO = require('socket.io');
var io = socketIO();
app.io = io;
var env = process.env.NODE_ENV || 'development';
app.locals.ENV = env;
app.locals.ENV_DEVELOPMENT = env == 'development';
// view engine setup, in this case we use handlebars.
// used mainly for initial page load in this example.
app.engine('handlebars', exphbs({
defaultLayout: 'main',
partialsDir: ['views/partials/']
}));
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'handlebars');
// app.use(favicon(__dirname + '/public/img/favicon.ico'));
app.use(logger('dev'));
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({
extended: true
}));
app.use(cookieParser());
/**
* We could bind the MSTHttpInterface as a middleware to Express. But for the
* purpose of the demo, we only use the websocket interface right now.
* Developing both would be too complex in the limited time available
*/
//app.use(MSTHttpInterface(mstApp));
//This is where the static files are served from
app.use(express.static(path.join(__dirname, 'public')));
//The default routes are handled by routes/index.js
app.use('/', routes);
/**
* Here we overwrite the /users route, so that it redirects to something else.
* You could couple this to another usermanager.
*/
app.use('/users', users);
/// catch 404 and forward to error handler
app.use(function(req, res, next) {
var err = new Error('Not Found');
err.status = 404;
next(err);
});
/// error handlers
// development error handler
// will print stacktrace
if (app.get('env') === 'development') {
app.use(function(err, req, res, next) {
res.status(err.status || 500);
res.render('error', {
message: err.message,
error: err,
title: 'error'
});
});
}
// production error handler
// no stacktraces leaked to user
app.use(function(err, req, res, next) {
res.status(err.status || 500);
res.render('error', {
message: err.message,
error: err,
title: 'error'
});
});
/**
* When a websocket connection is initialized handle it through
* multiscreen/mst-socket-interface.js
*/
io.on('connection', MSTSocketInterface(mstApp));
module.exports = app;