paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 47 Packages Projects Releases Wiki Activity

docs/backend-system: review fixes

Browse Source 
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
Patrik Oldsberg
2023-09-13 12:24:08 +02:00
parent 762e96ecdb
commit 52f715c9f2
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/backend-system/architecture/03-services.md
+1 -1
View File
@@ -194,7 +194,7 @@ When defining a default factory for a service, it is possible for it to end up w
## Service Factory Options
> NODE: This pattern is discouraged, only use it when necessary. If possible you should prefer to make services configurable via static configuration instead.
> NOTE: This pattern is discouraged, only use it when necessary. If possible you should prefer to make services configurable via static configuration instead.
When declaring a service factory it's possible to include an options callback. This allows you to customize the factory through code when installing it in the backend. For example, this is how you install an explicit factory instance in the backend without any options:
docs/backend-system/building-backends/01-index.md
+1 -1
View File
@@ -36,7 +36,7 @@ backend.start();
There will be a couple more plugins and modules in the initial setup, but the overall layout is the same.
What we're doing in this file is creating a new backend using `createBackend`, and then installing a collection of different plugins, modules, and service that we want to be part of that backend. Plugins are standalone features, modules augment existing plugins, while services can be used to override behavior for deeper customizations. Each module can only target a single plugin, and that plugin must also be present in the same backend. Finally, we start up the backend by calling the `start` method.
What we're doing in this file is creating a new backend using `createBackend`, and then installing a collection of different plugins, modules, and services that we want to be part of that backend. Plugins are standalone features, modules augment existing plugins or modules, while services can be used to override behavior for deeper customizations. Each module can only target a single plugin, and that plugin must also be present in the same backend. Finally, we start up the backend by calling the `start` method.
## Customization