'use strict';
class HTTP
{
constructor ()
{
// Dependencies
const Website = require('express')();
// Configure
Website.set('views', '../../public/views');
Website.set('view engine', 'ejs');
Website.use(require('body-parser').json());
Website.use(require('body-parser').urlencoded( { extended : false }));
Website.use(require('cookie-parser')());
// Load Middleware
require('glob').sync('./middleware/**/*.js').forEach (function (file) {
const Class = require(file);
new Class(Website);
});
// Load Routes
require('glob').sync(__dirname + '/controllers/**/*.js').forEach (function (file) {
const Class = require(file);
new Class(Website);
});
Website.listen(80, '0.0.0.0');
}
}
module.exports = HTTP;
Looking goodUpdates
- ES6 rewrite is complete
- Amazing speed increases by redoing my middle-ware and cleaning up classes
- Sessions are now ip_based and can be deleted by superior staff
- Useful if an account is hijacked, you can just end that session and lock the account
- Github merge coming after hotel_user features are finished
IP based? If that means what I think it means then it's a bad idea... especially for a admin panel, anybody on your network can use it if you're logged on. But I probably just misunderstood what you meant by that.Updates
- ES6 rewrite is complete
- Amazing speed increases by redoing my middle-ware and cleaning up classes
- Sessions are now ip_based and can be deleted by superior staff
- Useful if an account is hijacked, you can just end that session and lock the account
- Github merge coming after hotel_user features are finished
I'm just asking out of curiosity, but is it bad practice to do something like this instead of requiring the same modules on every single file:
const express = require('express')
const app = express()
const mongoose = require('mongoose')
mongoose.connect("mongodb://127.0.0.1:27017/test-app")
var globals = {
// Require dependencies
"express": express,
"app": app,
"server": require('http').Server(app),
"path": require('path'),
"mongoose": mongoose,
"session": require('express-session'),
"passport": require('passport'),
"local": require('passport-local').Strategy,
"bodyParser": require('body-parser'),
"validator": require('express-validator'),
"flash": require('connect-flash'),
"bcrypt": require('bcryptjs'),
"User": require(__dirname + '/models/user')
}
module.exports = globals// Require $
var $ = require(__dirname + '/app/globals')
//Set our static file directory to public
$.app.use($.express.static(__dirname + '/public'))Yes, that is what I was doing. You require the modules once and it's cached - but it's bad to use global variables. or to do that.
Yeah, I was just wondering.
Definitely not throwing shade at our favorite Dane <3 @Sentinel
Updates
- Bookshelf mode fix-ups
- Added panel customization features again
- Users and groups (panel) are about a quarter of the way finished.
@Jaden should I continue storing CRUD features in controllers, or put them in their respective database model?
When the beginner looks up a stack overflow article, and believes you should wrap everything in an arrow function or that you shouldn't always use the strict compiler.
If you're not too much of a moron, you can easily wrap Electron around Express, it's just stupid. So first, before you're trying to sound smart, get your facts straight first kiddo. Second of all, everybody knows streaming torrents is illegal, but yet again who the hell cares?
How can you even say that it's horribly done, when I haven't posted any code snippets of the application itself? You really lack of intellect mate. Never said I was an experienced JavaScript developer compared to how you mention yourself as some OP full stack developer. An app is not done horribly wrong, just because you don't use React or Angular, you stupid moron.
