Speech as a package #416
977
index.js
|
|
@ -12,9 +12,9 @@ module.exports = (helmet, html, preloadedState) => {
|
||||||
${helmet.meta.toString()}
|
${helmet.meta.toString()}
|
||||||
${helmet.link.toString()}
|
${helmet.link.toString()}
|
||||||
<!--style sheets-->
|
<!--style sheets-->
|
||||||
<link rel="stylesheet" href="/assets/css/reset.css" type="text/css">
|
<link rel="stylesheet" href="/static/assets/css/reset.css" type="text/css">
|
||||||
<link rel="stylesheet" href="/assets/css/general.css" type="text/css">
|
<link rel="stylesheet" href="/static/assets/css/general.css" type="text/css">
|
||||||
<link rel="stylesheet" href="/assets/css/mediaQueries.css" type="text/css">
|
<link rel="stylesheet" href="/static/assets/css/mediaQueries.css" type="text/css">
|
||||||
<!--google font-->
|
<!--google font-->
|
||||||
<link href="https://fonts.googleapis.com/css?family=Roboto:300" rel="stylesheet">
|
<link href="https://fonts.googleapis.com/css?family=Roboto:300" rel="stylesheet">
|
||||||
</head>
|
</head>
|
||||||
|
|
@ -25,7 +25,7 @@ module.exports = (helmet, html, preloadedState) => {
|
||||||
<script>
|
<script>
|
||||||
window.__PRELOADED_STATE__ = ${JSON.stringify(preloadedState).replace(/</g, '\\\u003c')}
|
window.__PRELOADED_STATE__ = ${JSON.stringify(preloadedState).replace(/</g, '\\\u003c')}
|
||||||
</script>
|
</script>
|
||||||
<script src="/bundle/bundle.js"></script>
|
<script src="/static/bundle/bundle.js"></script>
|
||||||
</body>
|
</body>
|
||||||
</html>
|
</html>
|
||||||
`;
|
`;
|
||||||
|
|
|
||||||
|
|
@ -47,14 +47,14 @@ 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.
|
|||||||
// set HTTP headers to protect against well-known web vulnerabilties
|
// set HTTP headers to protect against well-known web vulnerabilties
|
||||||
app.use(helmet());
|
app.use(helmet());
|
||||||
// 'express.static' to serve static files from public directory
|
// 'express.static' to serve static files from public directory
|
||||||
if (siteConfig.routes.public) {
|
if (siteConfig.routes.publicFolder) {
|
||||||
|
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.
|
|||||||
// take in a different public folder, so it can serve it's own bundle if needed
|
// take in a different public folder, so it can serve it's own bundle if needed
|
||||||
const { publicFolder } = siteConfig.routes;
|
const publicFolder = Path.resolve(process.cwd(), siteConfig.routes.publicFolder);
|
||||||
|
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.
|
|||||||
app.use(express.static(publicFolder))
|
app.use('/static', express.static(publicFolder));
|
||||||
|
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.info('serving static files from custom path:', publicFolder);
|
logger.info('serving static files from custom path:', publicFolder);
|
||||||
} else {
|
} else {
|
||||||
const publicPath = Path.resolve(__dirname, 'public');
|
const publicPath = Path.resolve(__dirname, 'public');
|
||||||
app.use(express.static(publicPath));
|
app.use('/static', express.static(publicPath));
|
||||||
|
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.info('serving static files from default path:', publicPath);
|
logger.info('serving static files from default path:', publicPath);
|
||||||
};
|
};
|
||||||
// 'body parser' for parsing application/json
|
// 'body parser' for parsing application/json
|
||||||
|
|
|
||||||
|
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?