-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server side rendering #405
Comments
If it works in development, the only difference can only be in deployment and configuration. Is the |
Indeed it was. It created an odd half created page, with parts missing. Ghastly, really. I'll pull up a test instance to see how it goes these days. |
Very sporky. If you get it to half-break again, care to paste the HTML as received from the server? I suspect some data fetches fail, or don't have the proper guarantees (see below) set. kerrokantasi-ui/src/views/QuestionView.js Lines 15 to 43 in 496ed86
|
This seems to tie into #410. An executive decision should probably be made about how to tackle SSR. It shouldn't be impossible to use a compiled Webpack bundle as a server-side renderer either, mind... |
There's no need for this atm apart from the metadata tags, which already has issue #317 . Shouldn't need whole SSR to do that. |
As Riku, I want the server side rendering to work on the server, not just in development. As end user, I want to share hearings so that picture and other data are available in the facebook share.
The text was updated successfully, but these errors were encountered: