Storyblok and hosting bundle updates

blog/2026-03-20-storyblok-adapters.mdx

@@ -32,6 +32,6 @@ The Storyblok docs now include a complete guide for the adapter-based setup.
 [7]: /docs/php/symfony/storyblok/more-features/id-slug-mapper
 [8]: /docs/php/symfony/storyblok/more-features/request-validator
 [9]: /docs/php/symfony/storyblok/more-features/backend-edit-url-helper
-[10]: /docs/php/symfony/storyblok/definitions-synced-event
+[10]: /docs/php/symfony/storyblok/component-sync#definitions-synced-event
 [12]: /docs/php/symfony/storyblok/asset-proxy
 [13]: /docs/php/symfony/storyblok/more-features

blog/2026-08-18-hosting-storyblok.mdx

@@ -0,0 +1,14 @@
+---
+title: "Storyblok & Hosting Bundle Updates"
+authors: [jannik]
+tags: [symfony, storyblok, hosting]
+---
+
+The hosting bundle now has `deploy-container` and `deploy-app` hooks. [Read the docs to understand the difference][1].
+
+The first usage of `deploy-app` hooks is in the Storyblok bundle: it now has [automatic component sync][2].
+
+
+
+[1]: /docs/php/symfony/hosting/#deploy-app-vs-container
+[2]: /docs/php/symfony/storyblok/component-sync#automatic-sync

docs/php/library/html-builder/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # HTML Builder
 

docs/php/library/lenient-front-matter/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Lenient Front Matter
 

docs/php/symfony/bundle-helpers/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Bundle Helpers
 

docs/php/symfony/cli/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # CLI
 

docs/php/symfony/embed-helpers/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Embed Helpers
 

docs/php/symfony/feature-flags/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Feature Flags
 

docs/php/symfony/hosting/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Hosting
 
@@ -126,10 +126,11 @@ These are called using the console commands:
 
 ```shell
 bin/console hosting:hook:build
-bin/console hosting:hook:deploy
+bin/console hosting:hook:deploy-container
+bin/console hosting:hook:deploy-app
 ```
 
-You can integrate into them by implementing the `BuildHookInterface` or `DeployHookInterface` interfaces respectively. Use autoconfiguration, then everything works out-of-the-box.
+You can integrate into them by implementing the `BuildHookInterface`, `DeployContainerHookInterface` or `DeployAppHookInterface` interfaces respectively. Use autoconfiguration, then everything works out-of-the-box.
 
 Every task has basically a label and a callback that can perform certain tasks:
 
@@ -154,6 +155,13 @@ class MyBuildTask implements BuildHookInterface
 }
 ```
 
+#### Deploy App vs Container
+
+The `deploy-container` hook is for deploying a single container. An application can consist of multiple containers (like hub and worker) and this deploy task should run in every container on every start.
+
+The `deploy-app` hook however is for the init container in Kubernetes. It should run exactly once on every app deployment (and not per container).
+
+
 ### App Validation
 
 App validation is a CLI command intended to be used in your CI, where your app can verify that the app is internally configured correctly.

docs/php/symfony/rad/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # RAD Bundle
 

docs/php/symfony/simple-normalizer/index.mdx

@@ -1,5 +1,5 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
-import {AddedBadge} from "../../../../src/components/AddedBadge";
+import {LinkList} from "@components/Link/LinkList";
+import {AddedBadge} from "@components/AddedBadge";
 
 # Simple Normalizer
 

docs/php/symfony/snail/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Snail
 

docs/php/symfony/storyblok/cli.mdx

@@ -55,4 +55,4 @@ You can pass `--force` to automatically confirm the command. This can be used to
 :::
 
 On successful sync, the bundle dispatches `StoryblokDefinitionsSyncedEvent`.
-See [Definitions Synced Event](./definitions-synced-event) for listener setup.
+See [Definitions Synced Event](./component-sync#definitions-synced-event) for listener setup.

docs/php/symfony/storyblok/component-sync.mdx

@@ -0,0 +1,67 @@
+import {AddedBadge} from "@components/AddedBadge";
+
+# Component Sync
+
+## Automatic Sync
+
+<AddedBadge package="21torr/storyblok" version="5.3" />
+
+The Storyblok bundle integrates natively with the [hosting bundle] and offers an automatic sync when doing an app deployment:
+
+```shell
+bin/console hosting:hook:deploy-app
+```
+
+Before it actually syncs the components to Storyblok however, you need to enable the environments where the automatic sync is enabled:
+
+```yaml title="conf/packages/storyblok.yaml"
+storyblok:
+    sync_definitions_on_app_deploy:
+        staging: false
+        production: true
+```
+
+With this config the automatic sync is only enabled when deploying the app on production.[^1]
+
+
+## Manual Sync
+
+You can also manually sync the components using the CLI:
+
+```shell
+bin/console storyblok:definitions:sync
+```
+
+
+## Definitions Synced Event
+
+After a successful `storyblok:definitions:sync`, the bundle dispatches `StoryblokDefinitionsSyncedEvent`.
+
+### Event Data
+
+The event provides:
+
+- `io`: `TorrStyle` instance used by the sync command.
+- `adapter`: the adapter that was synced.
+
+### Listener Example
+
+```php
+use Symfony\Component\EventDispatcher\Attribute\AsEventListener;
+use Torr\Storyblok\Event\StoryblokDefinitionsSyncedEvent;
+
+#[AsEventListener]
+public function onDefinitionsSynced (StoryblokDefinitionsSyncedEvent $event) : void
+{
+	$event->io->writeln("Run post-sync work...");
+	$event->adapter->managementApi;
+}
+```
+
+### Notes
+
+- If multiple adapters are synced in one command run, one event is dispatched per adapter.
+- The event is only dispatched on successful sync.
+
+[hosting bundle]: /docs/php/symfony/hosting/
+[^1]: There is also a shortcut form `sync_definitions_on_app_deploy: false|true` that sets both settings at the same time.

docs/php/symfony/storyblok/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Storyblok
 
@@ -53,4 +53,4 @@ Continue with the [adapter guide](./adapters) for setup, usage and configuration
 The Storyblok bundle dispatches these events:
 
 - `StoryblokWebhookEvent` for incoming Storyblok webhooks ([Webhook docs](./webhook)).
-- `StoryblokDefinitionsSyncedEvent` after successful component sync ([Definitions Synced Event](./definitions-synced-event)).
+- `StoryblokDefinitionsSyncedEvent` after successful component sync ([Definitions Synced Event](./component-sync#definitions-synced-event)).

docs/php/symfony/task-manager/index.mdx

@@ -1,5 +1,5 @@
-import {LinkList} from "../../../../src/components/Link/LinkList";
-import {AddedBadge} from "../../../../src/components/AddedBadge";
+import {LinkList} from "@components/Link/LinkList";
+import {AddedBadge} from "@components/AddedBadge";
 
 # Task Manager
 

docs/php/tooling/janus-php.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Janus PHP
 

docs/php/tooling/php-cs-fixer.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # PHP-CS-Fixer
 

docs/ts-scss/atlantis/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Atlantis
 

docs/ts-scss/dune/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Dune
 

docs/ts-scss/janus-ts/index.mdx

@@ -1,4 +1,4 @@
-import {LinkList} from "../../../src/components/Link/LinkList";
+import {LinkList} from "@components/Link/LinkList";
 
 # Janus TS
 

docusaurus.config.js

@@ -14,6 +14,22 @@ const config = {
 
 	plugins: [
 		'docusaurus-plugin-sass',
+		function ()
+		{
+			return {
+				name: "tsconfig-paths",
+				configureWebpack ()
+				{
+					return {
+						resolve: {
+							tsConfig: {
+								configFile: require.resolve("./tsconfig.json"),
+							},
+						},
+					};
+				},
+			};
+		},
 	],
 
 	markdown: {

src/pages/index.tsx

@@ -6,7 +6,7 @@ import React from 'react';
 import clsx from 'clsx';
 import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
 import Layout from '@theme/Layout';
-import HomepageFeatures from '@site/src/components/HomepageFeatures';
+import HomepageFeatures from '@components/HomepageFeatures';
 
 
 function HomepageHeader ()

tsconfig.json

@@ -3,6 +3,11 @@
 	"extends": "@tsconfig/docusaurus/tsconfig.json",
 	"compilerOptions": {
 		"baseUrl": ".",
+		"paths": {
+			"@components/*": [
+				"./src/components/*"
+			]
+		},
 		"plugins": [
 			{
 				"name": "typescript-plugin-css-modules"