Speech as a package #416
|
|
@ -54,6 +54,4 @@ module.exports = (req, res) => {
|
|||
|
||||
// send the rendered page back to the client
|
||||
res.send(renderFullPage(helmet, html, preloadedState));
|
||||
|
||||
console.log('hello from spee.ch handlePageRender.jsx');
|
||||
};
|
||||
|
|
|
|||
|
|
@ -73,6 +73,4 @@ module.exports = (req, res) => {
|
|||
// send the rendered page back to the client
|
||||
res.send(renderFullPage(helmet, html, preloadedState));
|
||||
});
|
||||
|
||||
console.log('hello from spee.ch handleShowRender.jsx');
|
||||
};
|
||||
|
|
|
|||
|
|
@ -15,24 +15,10 @@ const siteConfig = require('siteConfig.js');
|
|||
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 slackConfig = require('slackConfig.js');
|
||||
|
||||
function Server () {
|
||||
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.
|
||||
};
|
||||
|
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.
|
||||
};
|
||||
|
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.configureSite = (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.
|
||||
};
|
||||
|
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 = () => {
|
||||
|
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 = () => {
|
||||
|
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.configureLogger = 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.configureMysql = 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.configureSite = 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.
|
||||
this.configureSlack = 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.createApp = () => {
|
||||
// create an Express application
|
||||
const app = express();
|
||||
|
|
|
|||
|
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.
|
||||
For these you can just do
Do we need to have any
maxAge? It would be nice if the user was never logged outI thought handlebars was removed?