Download the PHP package digicomp/league-flysystem without Composer

On this page you can find all versions of the php package digicomp/league-flysystem. 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 league-flysystem

DigiComp.League.Flysystem

This package contains a factory for the filesystem abstraction layer written by Frank de Jonge. See http://flysystem.thephpleague.com/

There are two possibilities to use filesystems.

1. To use a filesystem in your project, I suggest you create an interface:

    /**
     * @method array listFiles(string $path = '', boolean $recursive = false)
     * @method array listPaths(string $path = '', boolean $recursive = false)
     */
    interface MyFilesystemInterface extends FilesystemInterface {}

And configure it with your `Objects.yaml`:

While your `Settings.yaml` could look like this:

The array used as first parameter for the factory expects an "adapter" and allows a "filesystemConfig" - key and all 
constructor arguments needed for the instantiation of the configured adapter. 

All other keys will be treated as property setters for the adapter.

The second parameter is a list of plugins, which should be added to your filesystem. Without a package prefix, they
will be searched in `League\Flysystem\Plugin`. If you write something like `AcMe.Package:MyPlugin` the factory will
look for a plugin named `\AcMe\Package\FlysystemPlugin\MyPlugin`.

After that you can Flow let inject your filesystem for you:

    /**
     * @var AcMe\Package\MyFilesystemInterface
     * @Flow\Inject
     */
  1. You could use a named Filesystem. Most of the parts above still makes sense, but instead of passing configuration arrays to the factory you might configure it in a Filesystem.yaml and give it a name.

    And then in Objects.yaml use use a different factory method:

And: Don't forget to have a lot of fun.


All versions of league-flysystem with dependencies

PHP Build Version
Package Version
Requires digicomp/flowobjectresolving Version ~1.0
league/flysystem Version ~1.0
neos/flow Version ~5.3|~6.3
php Version ^7.2
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 digicomp/league-flysystem contains the following files

Loading the files please wait ....