Download the PHP package jardisadapter/filesystem without Composer

On this page you can find all versions of the php package jardisadapter/filesystem. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package filesystem

Jardis Filesystem

Build Status PHP Version

Part of Jardis — the Domain-Driven Design platform for PHP. You model your domain; Jardis generates the production-ready hexagonal code (DTOs, Command/Query handlers, repositories, persistence). This package is part of the open-source foundation that generated code runs on.

File operations without the framework. A lean filesystem abstraction for PHP covering local and S3-compatible storage — designed for applications that store uploads, manage assets, or sync backups. No Flysystem, no AWS SDK, no dependency bloat. Just cURL and PHP builtins.


Why This Filesystem?


Installation


Quick Start

Local Filesystem

S3-Compatible Storage

Multiple Backends

Advanced Configuration

For custom permissions, symlink settings, or other advanced options — use create() with a config object:


File Operations


Stream Support

For large files — no memory overhead:


Directory Operations


Visibility

Control file permissions (local: Unix chmod, S3: ACL):


Configuration

LocalConfig

S3Config

The secret is protected with #[\SensitiveParameter] and masked in var_dump() / debug output.


Error Handling

All exceptions implement FilesystemExceptionInterface — catch one, catch all:

Exception When
FileNotFoundException File or directory does not exist
UnableToReadException Read failure (permissions, I/O, S3 auth)
UnableToWriteException Write failure (permissions, disk full, S3)
UnableToDeleteException Delete failure
FilesystemException Base — path traversal, null byte, invalid config

Architecture

The user only sees FilesystemService + config objects. Internally, the orchestrator builds a pipeline of atomic invokable handlers — one __invoke per operation:

Each handler is an invokable object (__invoke) — independently testable, replaceable, composable. The orchestrator extracts closures via ->__invoke(...) and stores only the closures. No handler object survives as a property.


Security


Contracts

The package implements interfaces from jardissupport/contracts:

Interface Purpose
FilesystemServiceInterface Factory: local(), s3()
FilesystemInterface Full API (extends Reader + Writer)
FilesystemReaderInterface Read-only subset — inject this for read-only contexts
FilesystemWriterInterface Write-only subset

Jardis Kernel Integration

jardiscore/foundation is deleted. Its Handler\FilesystemHandler was ported 1:1 into jardiscore/kernel as Bootstrap\Handler\BuildFilesystemFromEnv, which the packer Bootstrap\BuildDomainKernelFromEnv composes into the DomainKernel. In a class extending {Domain}Context, the filesystem is available via resource():

DomainKernel::filesystem() is typed ?FilesystemServiceInterface (core/kernel/src/DomainKernel.php:106) — the return value is the instance or null, there is no third state; null means the adapter is not installed.

The kernel reads no ENV for this adapter. BuildFilesystemFromEnv takes no arguments and returns a stateless FilesystemService factory — the developer reads the FS_*/FS_S3_* variables above directly, builds the Config objects, and passes them to FilesystemService.

No singleton, no handler call in application code — the developer decides how many filesystem instances exist and how they are configured. resource()->filesystem() returns FilesystemServiceInterface.


Development


Documentation

Full documentation, guides, and API reference:

docs.jardis.io/en/adapter/filesystem


License

MIT License — free for any use, including commercial.

AI-Assisted Development

This package ships with a skill for Claude Code, Cursor, Continue, and Aider. Install it in your consuming project:

More details: https://docs.jardis.io/en/skills


All versions of filesystem with dependencies

PHP Build Version
Package Version
Requires php Version >=8.2
jardissupport/contracts Version ^1.0 || ^2.0
ext-curl Version *
ext-fileinfo Version *
ext-simplexml Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package jardisadapter/filesystem contains the following files

Loading the files please wait ...