17 KiB
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:
"require": {
...
"knplabs/knp-gaufrette-bundle": "dev-master"
},
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.)
<?php
// app/autoload.php
$loader->addClassMap(array(
'Knp\Bundle' => __DIR__.'/../vendor/bundles',
'Gaufrette' => __DIR__.'/../vendor/gaufrette/src',
// ...
));
Register the bundle
You must register the bundle in your kernel:
<?php
// app/AppKernel.php
public function registerBundles()
{
$bundles = array(
// ...
new Knp\Bundle\GaufretteBundle\KnpGaufretteBundle()
);
// ...
}
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
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
local:
directory: /path/to/my/filesystem
The defined adapters are then used to create the filesystems.
Configuring the Filesystems
# app/config/config.yml
knp_gaufrette:
adapters:
# ...
filesystems:
bar:
adapter: foo
alias: foo_filesystem
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:
$container->get('knp_gaufrette.filesystem_map')->get('bar');
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
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
local:
directory: /path/to/my/filesystem
create: true
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
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
safe_local:
directory: /path/to/my/filesystem
create: true
Service (service)
Allows you to use a user defined adapter service.
Parameters
id
The id of the service (required)
Example
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
service:
id: my.adapter.service
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
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
in_memory:
files:
'file1.txt': ~
'file2.txt':
content: Some content
checksum: abc1efg2hij3
mtime: 123456890123
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
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
gridfs:
mongogridfs_id: acme_test.gridfs
In your AcmeTestBundle, add following service definitions:
# src/Acme/TestBundle/Resources/config/services.yml
parameters:
acme_test.mongo.server: "mongodb://localhost:27017"
acme_test.mongo.options:
connect: true
acme_test.mongodb.name: "test_database"
acme_test.gridfs.prefix: "fs" #Default
services:
acme_test.mongo:
class: Mongo
arguments: [%acme_test.mongo.server%, %acme_test.mongo.options%]
acme_test.mongodb:
class: MongoDB
arguments: [@acme_test.mongo, %acme_test.mongodb.name%]
acme_test.gridfs:
class: MongoGridFS
arguments: [@acme_test.mongodb, %acme_test.gridfs.prefix%]
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 domainhosts
Available trackers
Example
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
mogilefs:
domain: foobar
hosts: ["192.168.0.1:7001", "192.168.0.2:7001"]
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
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
ftp:
host: example.com
username: user
password: pass
directory: /example/ftp
create: true
mode: FTP_BINARY
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
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
sftp:
sftp_id: acme_test.sftp
directory: /example/sftp
create: true
In your AcmeTestBundle, add following service definitions:
# src/Acme/TestBundle/Resources/config/services.yml
parameters:
acme_test.ssh.host: my_host_name
acme_test.ssh.username: user_name
acme_test.ssh.password: some_secret
services:
acme_test.ssh.configuration:
class: Ssh\Configuration
arguments: [%acme_test.ssh.host%]
acme_test.ssh.authentication:
class: Ssh\Authentication\Password
arguments: [%acme_test.ssh.username%, %acme_test.ssh.password%]
acme_test.ssh.session:
class: Ssh\Session
arguments: [@acme_test.ssh.configuration, @acme_test.ssh.authentication]
acme_test.sftp:
class: Ssh\Sftp
arguments: [@acme_test.ssh.session]
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
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
apc:
prefix: APC 'namespace' prefix
ttl: 0
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:
"require": {
...
"amazonwebservices/aws-sdk-for-php": "1.6.2"
},
Note that Gaufrette is not currently compatible with the v2 Amazon SDK (called "aws/aws-sdk-php").
Parameters
amazon_s3_id
: the id of the AmazonS3 service used for the underlying connectionbucket_name
: the name of the bucket to useoptions
: additional (optional) settingsdirectory
: the directory to use, within the specified bucketregion
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:
# app/config/config.yml
services:
amazonS3:
class: AmazonS3
arguments:
options:
key: '%aws_key%'
secret: '%aws_secret_key%'
Example
Once the service is set up use its key as the amazon_s3_id in the gaufrette configuration:
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
amazon_s3:
amazon_s3_id: amazonS3
bucket_name: foo_bucket
options:
directory: foo_directory
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.
Open Cloud (opencloud)
Adapter for OpenCloud (Rackspace)
Parameters
object_store_id
: the id of the object store servicecontainer_name
: the name of the container to usecreate_container
: iftrue
will create the container if it doesn't exist (defaultfalse
)detect_content_type
: iftrue
will detect the content type for each file (defaulttrue
)
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:
# app/config/config.yml
services:
opencloud.connection:
class: OpenCloud\OpenStack
arguments:
- %openstack_identity_url%
- {username: %openstack_username%, password: %openstack_password%, tenantName: %openstack_tenant_name%}
HPCloud:
# app/config/config.yml
services:
opencloud.connection.hpcloud:
class: OpenCloud\OpenStack
arguments:
- 'https://region-a.geo-1.identity.hpcloudsvc.com:123456/v2.0/' // check https://account.hpcloud.com/account/api_keys for identities urls
- {username: %hpcloud_username%, password: %hpcloud_password%, tenantName: %hpcloud_tenant_name%}
The username and password are your login credentials, not the api key. Your tenantName is your Project Name on the api keys page.
Rackspace:
# app/config/config.yml
services:
opencloud.connection.rackspace:
class: OpenCloud\Rackspace
arguments:
- 'https://identity.api.rackspacecloud.com/v2.0/'
- {username: %rackspace_username%, apiKey: %rackspace_apikey%}
Define ObjectStore service
HPCloud:
# app/config/config.yml
services:
opencloud.object_store:
class: OpenCloud\ObjectStoreBase
factory_service: opencloud.connection.hpcloud
factory_method: ObjectStore
arguments:
- 'Object Storage' # Object storage type
- 'region-a.geo-1' # Object storage region
- 'publicURL' # url type
Rackspace:
# app/config/config.yml
services:
opencloud.object_store:
class: OpenCloud\ObjectStoreBase
factory_service: opencloud.connection
factory_method: ObjectStore
arguments:
- 'cloudFiles' # Object storage type
- 'DFW' # Object storage region
- 'publicURL' # url type
Example
Finally you can define your adapter in configuration:
# app/config/config.yml
knp_gaufrette:
adapters:
foo:
opencloud:
object_store_id: opencloud.object_store
container_name: foo
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
# app/config/config.yml
knp_gaufrette:
adapters:
media_ftp:
ftp:
host: example.com
username: user
password: pass
directory: /example/ftp
create: true
mode: FTP_BINARY
media_apc:
apc:
prefix: APC 'namespace' prefix
ttl: 0
media_cache:
cache:
source: media_ftp
cache: media_apc
ttl: 7200
filesystems:
media:
adapter: media_cache
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 likegaufrette://…
(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
# app/config/config.yml
knp_gaufrette:
adapters:
backup: #...
amazon: #...
filesystems:
backup1:
adapter: backup
amazonS3:
adapter: amazon
stream_wrapper: ~
gaufrette://backup1/...
gaufrette://amazonS3/...
Example 2
We define the protocol as "data", all filesystem will still be served (by default)
# app/config/config.yml
knp_gaufrette:
filesystems:
#...
stream_wrapper:
protocol: data
data://backup1/...
data://amazonS3/...
Example 3
We define the protocol as data and define which filesystem(s) will be available
# app/config/config.yml
knp_gaufrette:
filesystems:
#...
stream_wrapper:
protocol: data
filesystems:
- backup1
data://backup1/... (works since it is defined above)
data://amazonS3/... (will not be available)
Example 4
We define the protocol as data and define which filesystems will be available using array keys to set domain aliases
# app/config/config.yml
knp_gaufrette:
filesystems:
#...
stream_wrapper:
protocol: data
filesystems:
backup: backup1
pictures: amazonS3
data://backup/...
data://pictures/...