GitBook: [master] 2 pages modified

christianalfoni · gitbook-bot · commit bfb9b3f16f33 · 2020-01-23T11:29:00.000Z
diff --git a/core/running-side-effects.md b/core/running-side-effects.md
@@ -91,7 +91,6 @@ It can be a good idea to not allow your side effects to initialize when they are
 ```typescript
 import * as firebase from 'firebase'
 
-// We use IIFE to hide the private "app" variable
 export const api = (() => {
   let app
 
@@ -133,35 +132,6 @@ export const onInitialize = async ({ effects }) => {
 Typically you explicitly communicate with effects from actions, by calling methods. But sometimes you need effects to know about the state of the application, or maybe some internal state in the effect should be exposed on your application state. Again we can take advantage of an **initialize** method on the effect:
 
 {% tabs %}
-{% tab title="overmind/effects.js" %}
-```javascript
-// We use an IIFE to isolate some variables
-export const socket = (() => {
-  _options
-  _ws
-  return {
-    initialize(options) {
-      _options = options
-      _ws = new WebSocket('ws://...')
-      _ws.onclose = () => options.onStatusChange('close')
-      _ws.onopen = () => options.onStatusChange('open')
-      _ws.addEventListener(
-        'message',
-        (event) => options.onMessage(event.data)
-      )
-    },
-    send(type, data) {
-      _ws.postMessage({
-        type,
-        data,
-        token: _options.getToken()
-      })
-    }
-  }
-})()
-```
-{% endtab %}
-
 {% tab title="overmind/onInitialize.js" %}
 ```typescript
 export const onInitialize = async ({ state, effects, actions }) => {
diff --git a/guides-1/server-side-rendering.md b/guides-1/server-side-rendering.md
@@ -103,3 +103,55 @@ export const onInitialize: OnInitialize = ({ state }) => {
 If you are using state first routing, make sure you prevent the router from firing off the initial route, as this is not needed.
 {% endhint %}
 
+## OnInitialize
+
+The `onInitialized` action does not run on the server. The reason is that it is considered a side effect you might not want to run, so we do not force it. If you do want to run an action as Overmind fires up both on the client and the server you can rather create a custom action for it.
+
+{% tabs %}
+{% tab title="overmind/actions.js" %}
+```javascript
+export const initialize = () => {
+  // Whatever...
+}
+```
+{% endtab %}
+
+{% tab title="client/index.js" %}
+```typescript
+import { createOvermind } from 'overmind'
+import { config } from './overmind'
+
+const overmind = createOvermind(config)
+overmind.actions.initialize()
+```
+{% endtab %}
+
+{% tab title="server/index.js" %}
+```javascript
+import { createOvermindSSR } from 'overmind'
+import { config } from '../client/overmind'
+
+export default async (req, res) => {
+  const overmind = createOvermindSSR(config)
+  await overmind.actions.initialize()
+
+  const html = renderToString(
+    // Whatever implementation your view layer provides
+  )
+
+  res.send(`
+<html>
+  <body>
+    <div id="app">${html}</div>
+    <script>
+      window.__OVERMIND_MUTATIONS = ${JSON.stringify(overmind.hydrate())}
+    </script>
+    <script src="/scripts/app.js"></script>
+  </body>
+</html>
+`)
+}
+```
+{% endtab %}
+{% endtabs %}
+
