AppPool user
No edit summary |
(Automatically adding template at the end of the page.) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
When running Turnkey you will want to | When running Turnkey, you will want to ensure that the user running the IIS Turnkey application and the IIS MDriven Server application has access to the file system. Do this by allowing the local user "IIS APPPOOL\{app pool name}" full control (create directories) access to the application root. | ||
If you do not want to allow | If you do not want to allow complete control of the application root, the following may be an alternative: | ||
* '''AppData''' - full control at application installation. You may limit the read/write access after installation and model upload are done. | |||
* '''Logs''' - read/write access | |||
* '''ModeCodeAssemblies''' - only used for CodeDress | |||
This applies to both the MDrivenServer and Turnkey. | |||
This is particularly important when using [[CodeDress]] - since the assemblies need to be copied. | |||
This is | |||
[[Category:MDriven Server]] | [[Category:MDriven Server]] | ||
{{Edited|July|12|2024}} | |||
Latest revision as of 15:27, 10 February 2024
When running Turnkey, you will want to ensure that the user running the IIS Turnkey application and the IIS MDriven Server application has access to the file system. Do this by allowing the local user "IIS APPPOOL\{app pool name}" full control (create directories) access to the application root.
If you do not want to allow complete control of the application root, the following may be an alternative:
- AppData - full control at application installation. You may limit the read/write access after installation and model upload are done.
- Logs - read/write access
- ModeCodeAssemblies - only used for CodeDress
This applies to both the MDrivenServer and Turnkey.
This is particularly important when using CodeDress - since the assemblies need to be copied.
This page was edited 91 days ago on 02/10/2024. What links here