NextGenSoftware.OASIS.API.Providers.MinIOOASIS
2.0.3
See the version list below for details.
dotnet add package NextGenSoftware.OASIS.API.Providers.MinIOOASIS --version 2.0.3
NuGet\Install-Package NextGenSoftware.OASIS.API.Providers.MinIOOASIS -Version 2.0.3
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.MinIOOASIS" Version="2.0.3" />
<PackageVersion Include="NextGenSoftware.OASIS.API.Providers.MinIOOASIS" Version="2.0.3" />
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.MinIOOASIS" />
paket add NextGenSoftware.OASIS.API.Providers.MinIOOASIS --version 2.0.3
#r "nuget: NextGenSoftware.OASIS.API.Providers.MinIOOASIS, 2.0.3"
#:package NextGenSoftware.OASIS.API.Providers.MinIOOASIS@2.0.3
#addin nuget:?package=NextGenSoftware.OASIS.API.Providers.MinIOOASIS&version=2.0.3
#tool nuget:?package=NextGenSoftware.OASIS.API.Providers.MinIOOASIS&version=2.0.3
NextGenSoftware.OASIS.API.Providers.MinIOOASIS
MinIO OASIS Provider — S3-compatible self-hosted object storage for OASIS holons and avatars via S3 REST API. https://oasisomniverse.one
Installation
dotnet add package NextGenSoftware.OASIS.API.Providers.MinIOOASIS
NuGet versions · Source project
Choose a published version compatible with the other OASIS packages in your application. This guide describes current source; older packages may not contain the same functionality.
Frameworks and dependencies
Declared target frameworks: net10.0.
Direct external package references:
NextGenSoftware.OASIS.API.Core- Shared S3 provider library (official
AWSSDK.S33.7.502)
Project references and conditional dependency versions are recorded in the source project. NuGet restore resolves packaged dependencies; do not mix arbitrary DLLs from different release graphs.
Integration and configuration
Use this package for the responsibility described above, alongside its owning OASIS runtime/provider integration. Inspect the source project's public APIs and owning component documentation for construction and configuration; this package installation command does not start an API server, authenticate an avatar or provision an external service.
Provider adapters require their respective service configuration and credentials. Runtime libraries require the host application's lifecycle and persistent paths where applicable. Supply only the settings actually required by the owning component; do not copy production DNA into a client or public release.
Encrypted storage configuration
The endpoint/access-key constructor requires OASIS_MINIO_STORAGE_KEY: canonical Base64 for a separately persisted 32-byte encryption key. Keep it in protected host configuration, independent of S3 signing credentials; retain the same key across restarts. The provider never generates or replaces this key. Alternatively pass a Func<byte[]> key resolver to the explicit constructor; return a temporary copy because its buffer is zeroed after copying.
Provision the bucket before activation. The adapter uses the shared S3 transport and record policy, encrypted values and opaque keyed indexes. Existing oasis-avatars/, oasis-avatar-details/, oasis-holons/ or oasis-indexes/ objects cause an explicit refusal before reads/writes in the new layout. Preserve them for a reviewed migration; no automatic reset, import or plaintext fallback occurs.
useSSL must agree with the endpoint scheme. An injected IAmazonS3 must use MaxErrorRetry=0; caller ownership is the default. Dispose the provider to zero its private key state, and dispose a caller-owned client separately. Activation validates an existing bucket; it does not create buckets. Default holon deletion remains soft; DeleteHolonSoftAsync(id, false) requests permanent deletion.
Native service acceptance is distinct from controlled SDK-response tests. The opt-in integration binding uses the canonical core storage suite, an isolated pre-existing empty bucket, explicit test key and independent empty-bucket checks. It retains original failed reports and does not sweep arbitrary bucket contents.
Errors and security
For APIs returning OASISResult<T>, check IsError, ErrorCode and Message; do not treat a failed result as success. Preserve useful diagnostics without logging access tokens, passwords or private keys. Keep secrets in the host's appropriate protected configuration or platform storage.
Platform requirements
Target-framework compatibility is not proof that every native dependency or external service works on every operating system. Check the selected version's platform assets and native/service requirements before deployment. Unity/mobile integrations require their supported platform layer and packaging workflow; a managed NuGet archive alone does not establish Android/iOS, IL2CPP or two-device convergence acceptance.
Troubleshooting
- Restore/assembly mismatch: pin a coherent set of package versions and inspect the dependency graph.
- Configuration or authentication error: inspect the owning component's result diagnostics and service requirements without exposing secrets.
- Native loading failure: verify OS/architecture and required native artifacts rather than suppressing the error.
- Missing functionality in an older version: compare the immutable released source and release notes, not only the moving Development branch.
Releases and further documentation
[Verified release matrix](https://github.com/NextGenSoftwareUK/OASIS/blob/Development/Docs/WIP/Release and Status/OASIS_RELEASE_STATUS.md) · [Documentation audit](https://github.com/NextGenSoftwareUK/OASIS/blob/Development/Docs/WIP/Release and Status/RELEASE_DOCUMENTATION_AUDIT.md)
Published NuGet versions are immutable. Updated documentation ships with a new unpublished package version after checked promotion and publication. This metadata-backed guide does not replace product-specific API examples or claim unverified platform tests.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- NextGenSoftware.OASIS.API.Core (>= 2.0.6)
- NextGenSoftware.OASIS.Common (>= 2.0.5)
- NextGenSoftware.OASIS.Providers.Shared.S3 (>= 2.0.1)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on NextGenSoftware.OASIS.API.Providers.MinIOOASIS:
| Package | Downloads |
|---|---|
|
NextGenSoftware.OASIS.API.Providers.ThreeFoldOASIS
Connects the OASIS to ThreeFold -- a peer-to-peer Internet infrastructure platform providing decentralised compute, storage, and networking via the TF Grid. Stores OASIS holons and avatar data on ThreeFold's sovereign, carbon-neutral, self-healing global cloud. Part of the OASIS HOT-Swappable Provider Architecture. Ecosystem: https://oasisomniverse.one |
GitHub repositories
This package is not used by any popular GitHub repositories.
NextGenSoftware.OASIS.API.Providers.MinIOOASIS v2.0.3
MinIO OASIS Provider — S3-compatible self-hosted object storage for OASIS holons and avatars via S3 REST API. https://oasisomniverse.one/
What's new since v2.0.2
- fix: preserve MinIO failures and soft-delete acknowledgement (2a5c3f1)
- MOVING DOCS AROUND (32a8004)
- refactor: consolidate encrypted S3 provider family and conformance (ba17814)
- Validate GUID native keys before avatar deletion in forty adapters (597758b)
Full changelog
https://github.com/NextGenSoftwareUK/OASIS/commits/master/Providers/Storage/NextGenSoftware.OASIS.API.Providers.MinIOOASIS