You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VSF_NUXT_APP_PORT=3000 # nuxt server port property
33
+
VSF_NUXT_APP_HOST=0.0.0.0 # nuxt server host property
34
+
```
35
+
36
+
#### Storefront and middleware endpoints configuration
37
+
```
38
+
VSF_STORE_URL=https://localhost:3000 # external base url
39
+
VSF_MIDDLEWARE_URL=https://localhost:3000/api/ # external middleware base url
40
+
VSF_SSR_MIDDLEWARE_URL=http://localhost:3000/api/ # internal middleware base url
41
+
```
42
+
**NOTE**: *For many infrastructures `middleware_url` and `ssr_middleware_url` will be the same, but sometimes they might be different. For example, when it comes to deployment using a rolling-update strategy on the Kubernetes cluster, the Kubernetes is probing SSR if it's already up. SSR is trying to call middleware using an external URL (market...storefrontcloud.io) rather than localhost:3000/API, while the middleware isn't available publicly yet, because the SSR didn't respond with 200 in the first place.*
NODE_TLS_REJECT_UNAUTHORIZED=0 # toggle TLS verification (eg. for a local development)
83
+
```
84
+
27
85
### 2. Setup store configuration
28
86
29
87
The `plugins/storeConfigPlugin.ts` plugin loads store configuration data from Magento and saves it into the Pinia store under the `$state.storeConfig` property. By default, the amount of data loaded from Magento is minimal to avoid over-fetching, but as your application grows, you might need to pull more data.
<p>This is an example paragraph. Anything in the <strong>body</strong> tag will appear on the page, just like this <strong>p</strong> tag and its contents.</p>
0 commit comments