Speech as a package #416
7
index.js
|
@ -21,15 +21,12 @@ function Server () {
|
|||
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) => {
|
||||
mysqlConfig.update(userConfig);
|
||||
};
|
||||
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.
|
||||
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);
|
||||
};
|
||||
this.configureSlack = (userConfig) => {
|
||||
slackConfig.update(userConfig);
|
||||
};
|
||||
this.configureClientBundle = () => {
|
||||
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.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.
|
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?