Skip to content

Commit 5b672c5

Browse files
authored
Resolve styleguide warnings
1 parent 234baae commit 5b672c5

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

15/umbraco-deploy/getting-started/deploy-settings.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -259,13 +259,13 @@ By default, user groups are not exported as schema items unless they are enabled
259259

260260
### AllowIgnoreDependenciesOperations {#allow-ignore-dependencies}
261261

262-
When restoring or transferring content, media or other items, Umbraco Deploy will by default make sure any dependencies that don't exist on the target environment will be included in the operation.
262+
When restoring/transferring content or other items, Deploy will ensure any dependencies that don't exist on the target environment are included in the operation.
263263

264-
For example, if you have a media picker on a content item, that references a media item that doesn't exist on the target environment yet, the media item will be created when only tranferring that content. This ensures the target environment doesn't end up with broken dependencies (references/links to other items that don't exist).
264+
Example: You have a media picker on a content item, that references a media item that doesn't exist on the target environment yet. The media item will be created when transferring only that content. This ensures the target environment doesn't end up with broken dependencies (references/links to other items that don't exist).
265265

266-
Ignoring these dependencies will result in only restoring or tranferring the selected item(s), which allows more control over what is included in the operation (which can resolve deployment issues with a large amount of content, media or other items).
266+
When these dependencies are ignored only the selected item(s) are restored/transferred. This allows more control over what is included in the operation. Ignoring dependencies can also help resolve deployment issues with a large amount of content, media, or other items.
267267

268-
You can configure which operations are allowed to ignore dependencies when these are performed in the backoffice. Note that ignoring dependencies can result in deployment errors (e.g. parent items that aren't included) or content with broken dependencies.
268+
You can configure which operations are allowed to ignore dependencies when these are performed in the backoffice. Ignoring dependencies can result in deployment errors (like parent items that aren't included) or content with broken dependencies.
269269

270270
* `None` - ignoring dependencies is not allowed (the default value if the setting is missing)
271271
* `Restore` - dependencies can only be ignored when restoring from upstream environments
@@ -368,15 +368,14 @@ You can amend this behavior using this setting:
368368

369369
### PostDeploySchemaOperation {#post-deploy-schema-operation}
370370

371-
After the Umbraco schema is deployed from the files on disk, the current environment might still have items that don't have a corresponding file on disk.
372-
371+
After the schema is deployed from the files on disk, the current environment might still have items that don't have corresponding files on disk.
373372
You can automatically perform an operation after a schema deployment to align this:
374373

375374
* `None` - no operation is performed
376375
* `CleanSchema` - items that don't have a corresponding file on disk will be deleted
377376
* `ExtractSchema` - all items will be written to files on disk
378377

379-
A common use-case will to be configure `CleanSchema` on local/development environments, so deleted schema items will be automatically cleaned, ensuring they aren't re-created again when one of the environments writes the item back to disk and deploys the changes. Take caution when using this value on a live environment though, because missing schema files could result in deleting all content (e.g. deleting a document type will delete all content of that type).
378+
A common use case is to configure `CleanSchema` on local/development environments. Deleted schema items will then be cleaned automatically, ensuring they aren't re-created when an environment writes the item back and deploys the changes. Take caution when using this value on a live environment, as missing schema files can result in additional deletions. Deleting a Document Type, for example, will also delete all content using that type.
380379

381380
### PreferLocalDbConnectionString
382381

0 commit comments

Comments
 (0)