Speech as a package #416
|
@ -2,7 +2,7 @@ const logger = require('winston');
|
|||
|
||||
function LoggerConfig () {
|
||||
this.logLevel = 'debug';
|
||||
this.configure = (config) => {
|
||||
this.update = (config) => {
|
||||
if (!config) {
|
||||
return logger.warn('No logger config received.');
|
||||
}
|
||||
|
|
|
@ -4,7 +4,7 @@ function mysql () {
|
|||
This should probably be This should probably be `new Mysql()` since it is a class function
|
||||
this.database = 'default';
|
||||
this.username = 'default';
|
||||
this.password = 'default';
|
||||
this.configure = (config) => {
|
||||
This should probably be This should probably be `new Mysql()` since it is a class function
|
||||
this.update = (config) => {
|
||||
This should probably be This should probably be `new Mysql()` since it is a class function
|
||||
if (!config) {
|
||||
return logger.warn('No MySQL config received.');
|
||||
}
|
||||
|
|
|||
This should probably be This should probably be `new Mysql()` since it is a class function
This should probably be This should probably be `new Mysql()` since it is a class function
|
|
@ -33,7 +33,7 @@ function SiteConfig () {
|
|||
thumbnailChannelId : 'default',
|
||||
uploadDirectory : '/home/lbry/Uploads',
|
||||
};
|
||||
this.configure = (config) => {
|
||||
this.update = (config) => {
|
||||
if (!config) {
|
||||
return logger.warn('No site config received.');
|
||||
}
|
||||
|
|
|
@ -5,7 +5,7 @@ function SlackConfig () {
|
|||
this.slackWebHook = 'default';
|
||||
this.slackErrorChannel = 'default';
|
||||
this.slackInfoChannel = 'default';
|
||||
this.configure = (config) => {
|
||||
this.update = (config) => {
|
||||
if (!config) {
|
||||
return winston.warn('No slack config received');
|
||||
}
|
||||
|
|
47
index.js
|
@ -9,30 +9,33 @@ const http = require('http');
|
|||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
const logger = require('winston');
|
||||
const requestLogger = require('middleware/requestLogger.js');
|
||||
|
||||
const loggerConfig = require('loggerConfig.js');
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
const mysqlConfig = require('mysqlConfig.js');
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
const siteConfig = require('siteConfig.js');
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
const slackConfig = require('slackConfig.js');
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
function Server () {
|
||||
this.configureLogger = (loggerConfig) => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
require('loggerConfig.js').configure(loggerConfig);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
}
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.configureMysql = (mysqlConfig) => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
require('mysqlConfig.js').configure(mysqlConfig);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.configureLogger = (userConfig) => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
loggerConfig.update(userConfig);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
};
|
||||
this.configureSiteDetails = (siteConfig) => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
require('siteConfig.js').configure(siteConfig);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.sessionKey = siteConfig.auth.sessionKey;
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.PORT = siteConfig.details.port;
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.configureMysql = (userConfig) => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
mysqlConfig.update(userConfig);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
};
|
||||
this.configureSlack = (slackConfig) => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
require('slackConfig.js').configure(slackConfig);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.configureSiteDetails = (userConfig) => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
siteConfig.update(userConfig);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
};
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.configureSlack = (userConfig) => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
slackConfig.update(userConfig);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
};
|
||||
this.configureClientBundle = () => {
|
||||
logger.info('configure the client here by passing in the bundle and configuring it, or better yet: taking in the components to use dynamically from here.');
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
}
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
logger.debug('configure the client here by passing in the bundle and configuring it, or better yet: taking in the components to use dynamically from here.');
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
};
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.configureModels = () => {
|
||||
logger.info('here is where you could add/overwrite the default models')
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
}
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
logger.debug('here is where you could add/overwrite the default models')
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
};
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.configureRoutes = () => {
|
||||
logger.info('here is where you could add/overwrite the default routes')
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
}
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
logger.debug('here is where you could add/overwrite the default routes')
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
};
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.createApp = () => {
|
||||
// create an Express application
|
||||
const app = express();
|
||||
|
@ -53,9 +56,10 @@ function Server () {
|
|||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
// configure passport
|
||||
const speechPassport = require('speechPassport');
|
||||
// initialize passport
|
||||
const sessionKey = siteConfig.auth.sessionKey;
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
app.use(cookieSession({
|
||||
name : 'session',
|
||||
keys : [this.sessionKey],
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
keys : [sessionKey],
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
maxAge: 24 * 60 * 60 * 1000, // i.e. 24 hours
|
||||
}));
|
||||
app.use(speechPassport.initialize());
|
||||
|
@ -84,12 +88,13 @@ function Server () {
|
|||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
};
|
||||
this.start = () => {
|
||||
const db = require('./models/');
|
||||
const PORT = siteConfig.details.port;
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
// sync sequelize
|
||||
db.sequelize.sync()
|
||||
// start the server
|
||||
.then(() => {
|
||||
this.server.listen(this.PORT, () => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
logger.info(`Server is listening on PORT ${this.PORT}`);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
this.server.listen(PORT, () => {
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
logger.info(`Server is listening on PORT ${PORT}`);
|
||||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
||||
});
|
||||
})
|
||||
.catch((error) => {
|
||||
|
|
|||
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
For these you can just do
For these you can just do
```
this.configureLogger = loggerConfig.update
```
Do we need to have any Do we need to have any `maxAge`? It would be nice if the user was never logged out
I thought handlebars was removed? I thought handlebars was removed?
it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed. it's still being used in one specific case: for sharing videos on twitter via cards, twitter needs an html page with a video player embedded, so I am using handlebars to generate that one page when needed.
I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely. I guess we don't need to, and it does make a better user experience if the user doesn't need to log back in ever day. I eliminated the maxAge so sessions should last indefinitely.
|
This should probably be
new Mysql()
since it is a class function