FileHub.Ftp 1.0.0

FileHub

A .NET storage abstraction. One API (IFileHub → FileDirectory → FileEntry) across local disk, in-memory, and cloud object storage — swap the driver, keep the code.

using FileHub.Local;

var hub = new LocalFileHub(@"C:\data");        // or: new MemoryFileHub();
var file = hub.Root.CreateFile("hello.txt");   // anywhere under the sandbox root
file.SetText("hi");

Console.WriteLine(file.ReadAllText());

Why

Most .NET apps end up with System.IO.File scattered across services, or coupled to a cloud SDK whose types leak into every layer. When the storage backend has to change — "move uploads to S3", "keep tests off the disk", "sandbox per-tenant data" — the refactor hurts because the boundary was never drawn.

FileHub draws it once. A service like ReportService(IFileHub hub) is written once, unit-tested against memory, run locally against disk, and deployed to the cloud against an object store — without a single line changing in the service.

What's in the box

• Drivers: FileHub.Local (disk), FileHub.Memory (in-process), FileHub.OracleObjectStorage (OCI), FileHub.Ftp (FTP server). Custom drivers implement two abstract classes.
• Sync + async on the same types. Async is the source of truth; sync delegates.
• Sandboxed by default — every hub has a root. .., absolute paths, and symlink escapes are rejected.
• Read-only on demand — dir.AsReadOnly() / file.AsReadOnly() wraps anything and blocks writes at runtime.
• DI integration — FileHub.DependencyInjection ships AddFileHub / AddNamedFileHubs with lifetime + IServiceProvider support for tenant scoping.
• Nested paths — CreateDirectory("a/b/c") and TryOpenDirectory("a/b/c", out _) work on every driver. DirectoryPathMode.Direct (default on cloud drivers) collapses it to a single API call.
• Zero external deps in core. Multi-targets netstandard2.0;net8.0.

Install

dotnet add package FileHub
dotnet add package FileHub.DependencyInjection    # optional
dotnet add package FileHub.OracleObjectStorage    # optional
dotnet add package FileHub.Ftp                    # optional

Named hubs (tenant, multi-backend)

services.AddNamedFileHubs(b => b
    .Register("reports", new MemoryFileHub())
    .Register(
        "tenant",
        sp => new LocalFileHub($@"C:\tenants\{sp.GetRequiredService<ITenantContext>().Id}"),
        ServiceLifetime.Scoped));

Inject INamedFileHubs and call GetByName("tenant").

Documentation

Full docs live in the wiki:

• Quick Start — install, hubs, files, directories
• API reference — IFileHub, FileDirectory, FileEntry, exceptions
• Drivers — Local, Memory, OCI, FTP
• Usage patterns — sync/async, streams, pagination
• Security — sandbox and read-only mode
• Dependency injection · Custom drivers · Testing

License

MIT — see LICENSE.txt.