Gaufrette provides a filesystem abstraction layer.
Imagine you have to manage a lot of medias in a PHP project. Lets see how to take this situation in your advantage using Gaufrette.
The filesystem abstraction layer permits you to develop your application without the need to know were all those medias will be stored and how.
Another advantage of this is the possibility to update the files location without any impact on the code apart from the definition of your filesystem. In example, if your project grows up very fast and if your server reaches its limits, you can easily move your medias in an Amazon S3 server or any other solution.
Read the official Gaufrette documentation.
Every maintained adapter now have a dedicated metapackage. You can find the list on packagist. We highly recommend you to use them as they contain their own requirements: you don't need to worry about third-party dependencies to install before using Gaufrette anymore.
Symfony integration is available through KnpLabs/KnpGaufretteBundle.
Here is the list of dedicated maintainer(s) for every adapter not deprecated. If you don't receive any response to your issue or pull request in a timely manner, ping us:
| Adapter | Referent |
|---|---|
| AwsS3 | @NiR- |
| AzureBlobStorage | @NiR- |
| DoctrineDbal | @pedrotroller, @NicolasNSSM |
| Flysystem | @nicolasmure |
| Ftp | @fabschurt |
| GoogleCloudStorage | @AntoineLelaisant |
| GridFS | @NiR- |
| InMemory | |
| Local | |
| OpenCloud | @NiR- |
| PhpseclibSftp | @fabschurt |
| Zip |
For InMemory, Local and Zip adapters everyone in this list is considered as a maintainer.
Requires:
- docker
- docker-compose
Build images:
$ docker-compose build
Launch the tests:
$ bin/tests-all
Is it green?
This project does not have any stable release yet but we do not want to break BC now.