Speech as a package #416
4
index.js
|
@ -50,7 +50,7 @@ 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.
|
||||
app.use(express.static(publicFolder));
|
||||
logger.info('serving static files from custom path:', publicFolder);
|
||||
} else {
|
||||
const publicPath = Path.resolve(process.cwd(), 'static');
|
||||
![]() 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 publicPath = Path.resolve(process.cwd(), 'public');
|
||||
![]() 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(express.static(publicPath));
|
||||
logger.warn(`serving static files from default static path at ${publicPath}. Please specify a path in your config/siteConfig.js file`, );
|
||||
};
|
||||
|
|
|||
![]() 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?