Menu

Individual skill

orchardcore-temp-file-storage

Skill for configuring and using Orchard Core 4.0 temporary file storage. Covers ITempDirectoryProvider, DefaultTempDirectoryProvider, the OrchardCore TempDirectory Path setting, tenant-scoped temporary directories, mounting Azure Files, AWS EFS or FSx and SMB or NFS shares, multi-instance TUS resumable uploads, ITusTempStore blob and S3 stores, consuming GetRootDirectory, GetTempFileName and CreateTempSubdirectory from module code, and replacing the default provider. Use this skill when requests mention Orchard Core temporary files, temp directory, Path.GetTempPath, disk full during uploads, TUS uploads across instances, MediaOptions TusTempPath, chunked uploads, deployment import temp files, or closely related Orchard Core implementation, setup, extension, or troubleshooting work. Strong matches include work with OrchardCore.FileStorage, ITempDirectoryProvider, DefaultTempDirectoryProvider, TempDirectoryOptions, OrchardCore.Media.Tus, and ITusTempStore.

src/CrestApps.AgentSkills/orchardcore/orchardcore-temp-file-storage/SKILL.md

Read pinned source

Source commit d86d04f234b1b2bd8145368a2544490f9d557596

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
13
Repository last updated
Oct 21, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Orchard Core Temporary File Storage - Prompt Templates

## Relocate and Use Temporary File Storage

You are an Orchard Core expert. Generate configuration and code for Orchard Core's shared temporary file storage.

### Guidelines

- Orchard Core 4.0 writes temporary files through `ITempDirectoryProvider` (namespace `OrchardCore.FileStorage`, package `OrchardCore.Infrastructure.Abstractions`): in-progress media chunked uploads, TUS resumable uploads, deployment and recipe import/export archives (local and remote), workflow type import/export, recipes written to disk before tenant setup (tenant API recipe uploads), PDF text extraction for media indexing, and ClamAV buffering of non-seekable uploads.
- The default `DefaultTempDirectoryProvider` stores files under `{Path}/{TenantName}/...`. The tenant sub-directory is added automatically; never compose it yourself. Tenants cannot see or collide with each other's files.
- Configure the base path with `OrchardCore:TempDirectory:Path` (bound to `TempDirectoryOptions`). When it is omitted, `Path.GetTempPath()` is used, which matches the previous behavior.
- On Unix-like systems, new tenant directories get owner-only permissions (`700`), like `Directory.CreateTempSubdirectory()`.
- Why it exists: the OS temporary volume is often small (system disks, ephemeral container disks) and could fill up under concurrent large uploads. A configurable path can also be a shared volume, so an upload started on one instance can be completed on another.
- Point `Path` at a mounted file share (local disk, SAN/NAS, Azure Files over SMB, AWS EFS/FSx over NFS), never at object storage. Consumers need seekable local files (`Seek`/`SetLength`, `ZipFile.ExtractToDirectory`, `PhysicalFileProvider`).