Download the PHP package tsslabs/knp-gaufrette-bundle without Composer

Gaufrette Bundle

Provides a Gaufrette integration for your Symfony projects.

About Gaufrette

Gaufrette is a PHP 5.3+ library providing a filesystem abstraction layer. This abstraction layer allows you to develop applications without needing to know where all their media files will be stored or how.

Documentation is available the official page of Gaufrette.

Installation

Prerequisites

As this bundle is an integration for Symfony of the Gaufrette library, it requires you to first install Gaufrette in a Symfony project.

Download the bundle

You can download an archive of the bundle and unpack it in the vendor/bundles/Knp/Bundle/GaufretteBundle directory of your application.

Standard Edition Style

If you are using the deps file to manage your project's dependencies, you must add the following lines to it:

[gaufrette]
    git=http://github.com/KnpLabs/Gaufrette.git

[KnpGaufretteBundle]
    git=http://github.com/KnpLabs/KnpGaufretteBundle.git
    target=/bundles/Knp/Bundle/GaufretteBundle

Composer Style

This bundle can be installed using composer by adding the following in the require section of your composer.json file:

Git Submodule Style

If you are versioning your project with git and making changes to this bundle you can embed it as a submodule:

$ git submodule add https://github.com/KnpLabs/KnpGaufretteBundle.git vendor/bundles/Knp/Bundle/GaufretteBundle

Add the namespace in the autoloader

You must register both Gaufrette and the KnpGaufretteBundle in your autoloader: (You do not have to do this if you are using the composer autoload system.)

Register the bundle

You must register the bundle in your kernel:

Configuration

The Gaufrette bundle allows you to declare your filesystems as services without having to reach into the famous "Service Container". Indeed, you can do it with the configuration!

The configuration of the Gaufrette bundle is divided into two parts: the adapters and the filesystems.

Configuring the Adapters

The defined adapters are then used to create the filesystems.

Configuring the Filesystems

Each defined filesystem must have an adapter with its value set to an adapter's key. The filesystem defined above will result in a service with id gaufrette.bar_filesystem. The alias parameter allows us to define an alias for it (foo_filesystem in this case).

The filesystem map

You can access all declared filesystems through the map service. In the previous exemple, we declared a bar filesystem:

Returns the bar instance of Gaufrette\Filesystem.

Adapters Reference

Local Adapter (local)

A simple local filesystem based adapter.

Parameters

• directory The directory of the filesystem (required)
• create Whether to create the directory if it does not exist (default true)

Example

Safe Local Adapter (safe_local)

Almost as simple as the local adapter, but it encodes key to avoid having to deal with the directories structure.

Parameters

• directory The directory of the filesystem (required)
• create Whether to create the directory if it does not exist (default true)

Example

Service (service)

Allows you to use a user defined adapter service.

Parameters

• id The id of the service (required)

Example

In Memory (in_memory)

Adapter for test purposes, it stores files in an internal array.

Parameters

• files An array of files (optional)

The files is an array of files where each file is a sub-array having the content, checksum and mtime optional keys.

Example

Azure Blob Storage (azure_blob_storage)

Adapter for Microsoft Azure Blob Storage service. To use this adapter you need to install the Azure SDK for php into your project.

Further more you need a valid connection string and you must define a Blob Proxy factory service with it. You can use the default \Gaufrette\Adapter\AzureBlobStorage\BlobProxyFactory this way:

You must set the parameter azure_blob_storage_connection_string to contain your windows azure blob storage connection string. You can retrieve your connection string in your Windows Azure management console.

Parameters

• blob_proxy_factory_id Reference to the blob proxy factory service
• container_name The name of the container
• create_container Boolean value that indicates whether to create the container if it does not exists (optional: default false)
• detect_content_type Boolean value that indicates whether to auto determinate and set the content type on new blobs (optional: default true)

Example

GridFS (gridfs)

Adapter that allows you to use a MongoDB GridFS for storing files.

Parameters

• mongogridfs_id The id of the service that provides MongoGridFS object instance for adapter (required)

Example

In your AcmeTestBundle, add following service definitions:

Note that it is possible to prepare MongoGridFS service any way you like. This is just one way to do it.

MogileFS (mogilefs)

Adapter that allows you to use MogileFS for storing files.

Parameters

• domain MogileFS domain
• hosts Available trackers

Example

Ftp (ftp)

Adapter for FTP.

Parameters

• directory The remote directory (required)
• host FTP host (required)
• username FTP username (default null)
• password FTP password (default null)
• port FTP port (default 21)
• passive FTP passive mode (default false)
• create Whether to create the directory if it does not exist (default false)
• mode FTP transfer mode (defaut FTP_ASCII)

Example

Sftp (sftp)

Adapter for SFTP (SSH-FTP).

Parameters

• sftp_id The id of the service that provides SFTP access.
• directory The remote directory (default null).
• create Whether to create the directory if it does not exist (default false).

Example

In your AcmeTestBundle, add following service definitions:

Apc (apc)

Adapter for APC.

A non-persistent adapter, use it in the dev environment, in demo sites, ...

Parameters

• prefix The prefix to this filesystem (APC 'namespace', it is recommended that this end in a dot '.') (required)
• ttl Time to live (default 0)

Example

Amazon S3 (amazon_s3)

Adapter to connect to Amazon S3 instances.

This adapter requires the use of amazonwebservices/aws-sdk-for-php which can be installed by adding the following line to your composer.json:

Parameters

• amazon_s3_id: the id of the AmazonS3 service used for the underlying connection
• bucket_name: the name of the bucket to use
• options: additional (optional) settings
  • directory: the directory to use, within the specified bucket
  • region
  • create

Defining services

To use the Amazon S3 adapter you need to provide a valid AmazonS3 instance (as defined in the Amazon SDK). This can easily be set up as using Symfony's service configuration:

Example

Once the service is set up use its key as the amazon_s3_id in the gaufrette configuration:

Note that the SDK seems to have some issues with bucket names with dots in them, e.g. "com.mycompany.bucket" seems to have issues but "com-mycompany-bucket" works.

AwsS3

Adapter for Amazon S3 SDK v2.

Parameters

• service_id The service id of the Aws\S3\S3Client to use. (required)
• bucket_name The name of the S3 bucket to use. (required)
• options A list of additional options passed to the adapter.
  • create Whether to create the bucket if it doesn't exist. (default false)
  • directory A directory to operate in. (default '') This directory will be created in the root of the bucket and all files will be read and written there.

Example

Open Cloud (opencloud)

Adapter for OpenCloud (Rackspace)

Parameters

• object_store_id: the id of the object store service
• container_name: the name of the container to use
• create_container: if true will create the container if it doesn't exist (default false)
• detect_content_type: if true will detect the content type for each file (default true)

Defining services

To use the OpenCloud adapter you should provide a valid ObjectStore instance. You can retrieve an instance through the OpenCloud\OpenStack or OpenCloud\Rackspace instances. We can provide a comprehensive configuration through the Symfony DIC configuration.

Define OpenStack/Rackspace service

Generic OpenStack:

HPCloud:

The username and password are your login credentials, not the api key. Your tenantName is your Project Name on the api keys page.

Rackspace:

Define ObjectStore service

HPCloud:

Rackspace:

Example

Finally you can define your adapter in configuration:

Cache (cache)

Adapter which allows you to cache other adapters

Parameters

• source The source adapter that must be cached (required)
• cache The adapter used to cache the source (required)
• ttl Time to live (default 0)
• serializer The adapter used to cache serializations (default null)

Example

Stream Wrapper

The stream_wrapper settings allow you to register filesystems with a specified domain and then use as a stream wrapper anywhere in your code like: gaufrette://domain/file.txt

Parameters

• protocol The protocol name like gaufrette://… (default gaufrette)
• filesystem An array that contains filesystems that you want to register to this stream_wrapper. If you set array keys these will be used as an alias for the filesystem (see examples below) (default all filesystems without aliases)

Example 1

Using default settings, the protocol is "gaufrette" and all filesystems will be served

Example 2

We define the protocol as "data", all filesystem will still be served (by default)

Example 3

We define the protocol as data and define which filesystem(s) will be available

Example 4

We define the protocol as data and define which filesystems will be available using array keys to set domain aliases

Doctrine DBAL (doctrine_dbal)

Adapter that allows you to store data into a database.

Parameters

• connection_name The doctrine dbal connection name like default
• table The table name like media_data
• key: The primary key in the table
• content: The field name of the file content
• mtime: The field name of the timestamp
• checksum: The field name of the checksum

Example