Skip to content
Symfony bundle integrating Flysystem into Symfony 4.2+ applications
Branch: master
Clone or download
tgalopin Merge pull request #6 from nclsHart/fix-next-link
Fix next link in caching metadata doc
Latest commit 1b976c2 Apr 20, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
src Remove unecessary DefinitionFactory circular reference in Adapter def… Apr 19, 2019
tests Remove unecessary DefinitionFactory circular reference in Adapter def… Apr 19, 2019
.gitignore Update README Apr 9, 2019
.travis.yml Write README and start documentation Apr 7, 2019
LICENSE Update README Apr 17, 2019
composer.json Update README Apr 9, 2019
phpunit.xml.dist Initial commit Apr 7, 2019


Build Status Packagist Version Software license


This repository is a light Symfony bundle integrating the Flysystem library into Symfony applications. It provides an efficient abstraction for the filesystem, for instance to use local files in development and a cloud storage in production or to use a memory filesystem in tests to increase their speed.

This bundle relies on named aliases (introduced in Symfony 4.2) in order to create and configure multiple filesystems while still following the best practices of software architecture (SOLID principles).


flysystem-bundle requires PHP 7.1+ and Symfony 4.2+.

You can install the bundle using Symfony Flex:

composer require league/flysystem-bundle


  1. Getting started
  2. Cloud storage providers: Azure, AWS S3, DigitalOcean Spaces, Scaleway Object Storage, Google Cloud Storage, Rackspace, WebDAV
  3. Interacting with FTP and SFTP servers
  4. Caching metadata in Symfony cache
  5. Creating a custom adapter

Security Issues

If you discover a security vulnerability within the bundle, please follow our disclosure procedure.

Backward Compatibility promise

This library follows the same Backward Compatibility promise as the Symfony framework:

Note: many classes in this bundle are either marked @final or @internal. @internal classes are excluded from any Backward Compatiblity promise (you should not use them in your code) whereas @final classes can be used but should not be extended (use composition instead).

You can’t perform that action at this time.