Skip to content

Commit d135aec

Browse files
authored
Update 15/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md
1 parent 38cd9b2 commit d135aec

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

15/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ This means that you should avoid making files on the fly, and instead rely on bu
2323

2424
In an Umbraco context, this means you should not create or edit template, script or stylesheet files via the backoffice. These should be deployed as part of your web application and not managed via Umbraco.
2525

26-
Similarly, you shouldn't use InMemory modelsbuilder, since that also relies on creating files on the disk. While this is not a hard requirement, it doesn't provide any value if not live editing your site.
26+
Similarly, you shouldn't use InMemory modelsbuilder, since that also relies on creating files on the disk. While this is not a hard requirement, it doesn't provide any value unless you are live editing your site.
2727

2828
Instead, configure models builder to use use "source code" mode in development, and "none" in production, as [described when using runtime modes](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/runtime-modes).
2929

0 commit comments

Comments
 (0)