Welcome to Flask-FS’s documentation!¶
Flask-FS provide a simple and flexible file storage interface for Flask. It is inspired by Django file storage.
Documentation¶
This part of the documentation will show you how to get started in using Flask-FS with Flask.
Installation¶
Install Flask-FS with pip
:
pip install flask-fs
Each backend has its own dependencies:
$ pip install flask-fs[s3] # For Amazon S3 backend support
$ pip install flask-fs[swift] # For OpenStack swift backend support
$ pip install flask-fs[gridfs] # For GridFS backend support
$ pip install flask-fs[all] # To include all dependencies for all backends
The development version can be downloaded from GitHub.
git clone https://github.com/noirbizarre/flask-fs.git
cd flask-fs
pip install -e .[dev]
Flask-FS requires Python version 2.6, 2.7, 3.3, 3.4 or 3.5. It’s also working with PyPy and PyPy3.
Quick Start¶
Initialization¶
Flask-FS need to be initialized with an application:
from flask import Flask
import flask_fs as fs
app = Flask(__name__)
fs.init_app(app)
Storages declaration¶
You need to declare some storages before being able to read or write files.
import flask_fs as fs
images = fs.Storage('images')
uploads = fs.Storage('uploads')
You can limit the allowed file types.
import flask_fs as fs
images = fs.Storage('images', fs.IMAGES)
custom = fs.Storage('custom', ('bat', 'sh'))
You can also specify allowed extensions by exclusion:
import flask_fs as fs
WITHOUT_SCRIPTS = fs.AllExcept(fs.SCRIPTS + fs.EXECUTABLES)
store = fs.Storage('store', WITHOUT_SCRIPTS)
By default files in storage are not overwritables.
You can allow overwriting with the overwrite parameter in Storage
class.
import flask_fs as fs
store = fs.Storage('store', overwrite=True)
Storages operations¶
Storages provides an abstraction layer for common operations. All filenames are root relative to the storage.
store = fs.Storage('store')
# Writing
store.write('my.file', 'content')
# Reading
content = store.read('my.file')
# Working with file object
with store.open('my.file', 'wb') as f:
# do something
# Testing file presence
if store.exists('my.file'):
# do something
if 'my.file' in store:
# do something
# Deleting file
store.delete('my.file')
See Storage
class definition.
Configuration¶
Flask-FS expose both global and by storage settings.
Global configuration¶
FS_ROOT¶
default: {app.instance_path}/fs
The global local storage root. Each storage will have its own root as a subdirectory unless not local or overridden by configuration.
FS_URL¶
default: None
An optionnal URL on which the FS_ROOT is visible (ex: 'https://static.mydomain.com/'
).
FS_BACKEND¶
default: 'local'
The default backend used for storages.
Can be one of local
, s3
, gridfs
or swift
Storages configuration¶
Each storage configuration can be overriden from the application configuration. The configuration is loaded in the following order:
FS_{BACKEND_NAME}_{KEY}
(backend specific configuration){STORAGE_NAME}_FS_{KEY}
(specific configuration)FS_{KEY}
(global configuration)- default value
Given a storage declared like this:
import flask_fs as fs
avatars = fs.Storage('avatars', fs.IMAGES)
You can override its root with the following configuration:
AVATARS_FS_ROOT = '/somewhere/on/the/filesystem'
Or you can set a base URL to all storages for a given backend:
FS_S3_URL = 'https://s3.somewhere.com/'
FS_S3_REGION = 'us-east-1'
Backends¶
Local backend (local
)¶
A local file system storage. This is the default storage backend.
Expect the following settings:
ROOT
: The file system root
S3 backend (s3
)¶
An Amazon S3 Backend (compatible with any S3-like API)
Expect the following settings:
ENDPOINT
: The S3 API endpointREGION
: The region to work on.ACCESS_KEY
: The AWS credential access keySECRET_KEY
: The AWS credential secret key
GridFS backend (gridfs
)¶
A Mongo GridFS backend
Expect the following settings:
MONGO_URL
: The Mongo access URLMONGO_DB
: The database to store the file in.
Swift backend (swift
)¶
An OpenStack Swift backend
Expect the following settings:
AUTHURL
: The Swift Auth URLUSER
: The Swift user inKEY
: The user API Key
Custom backends¶
Flask-FS allows you to defined your own backend
by extending the BaseBackend
class.
You need to register your backend using setuptools entrypoints in your setup.py
:
entry_points={
'fs.backend': [
'custom = my.custom.package:CustomBackend',
]
},
Sample configuration¶
Given these storages:
import flask_fs as fs
files = fs.Storage('files')
avatars = fs.Storage('avatars', fs.IMAGES)
images = fs.Storage('images', fs.IMAGES)
Here an example configuration with local files storages and s3 images storage:
# Shared S3 configuration
FS_S3_ENDPOINT = 'https://s3-eu-west-2.amazonaws.com'
FS_S3_REGION = 'eu-west-2'
FS_S3_ACCESS_KEY = 'ABCDEFGHIJKLMNOQRSTU'
FS_S3_SECRET_KEY = 'abcdefghiklmnoqrstuvwxyz1234567890abcdef'
FS_S3_URL = 'https://s3.somewhere.com/'
# storage specific configuration
AVATARS_FS_BACKEND = 's3'
IMAGES_FS_BACKEND = 's3'
FILES_FS_URL = 'https://images.somewhere.com/'
FILES_FS_URL = 'https://files.somewhere.com/'
In this configuration, storages will have the following configuration:
files
:local
storage served onhttps://files.somewhere.com/
avatars
:s3
storage served onhttps://s3.somewhere.com/avatars/
images
:s3
storage served onhttps://images.somewhere.com/
Mongoengine support¶
Flask-FS provides a thin mongoengine integration as field classes
.
Both FileField
and ImageField
provides a common interface:
images = fs.Storage('images', fs.IMAGES,
upload_to=lambda o: 'prefix',
basename=lambda o: 'basename')
class MyDoc(Document):
file = FileField(fs=files)
doc = MyDoc()
# Test file presence
print(bool(doc.file)) # False
# Get filename
print(doc.file.filename) # None
# Get file URL
print(doc.file.url) # None
# Print file URL
print(str(doc.file)) # ''
doc.file.save(io.Bytes(b'xxx'), 'test.file')
print(bool(doc.file)) # True
print(doc.file.filename) # 'test.file'
print(doc.file.url) # 'http://myserver.com/files/prefix/test.file'
print(str(doc.file)) # 'http://myserver.com/files/prefix/test.file'
# Override Werkzeug Filestorage filename with basename
f = FileStorage(io.Bytes(b'xxx'), 'test.file')
doc.file.save(f)
print(doc.file.filename) # 'basename.file'
The ImageField
provides some extra features.
On declaration:
- an optionnal max_size attribute allows to limit image size
- an optionnal thumbnails list of thumbnail sizes to be generated
- an optionnal optimize booleanoverriding the
FS_IMAGES_OPTIMIZE
setting by field.
On instance:
- the original property gives the unmodified image filename
- the best_url(size) method match a thumbnail URL given a size
- the thumbnail(size) method get a thumbnail filename given a registered size
- the save method accept an optionnal bbox kwarg for to crop the thumbnails
- the rerender method allows to force a new image rendering (taking in account new parameters)
- the instance is callable as shortcut for best_url()
images = fs.Storage('images', fs.IMAGES)
files = fs.Storage('files', fs.ALL)
class MyDoc(Document):
image = ImageField(fs=images,
max_size=150,
thumbnails=[100, 32])
doc = MyDoc()
with open(some_image, 'rb') as f:
doc.file.save(f, 'test.png')
print(doc.image.filename) # 'test.png'
print(doc.image.original) # 'test-original.png'
print(doc.image.thumbnail(100)) # 'test-100.png'
print(doc.image.thumbnail(32)) # 'test-32.png'
# Guess best image url for a given size
assert doc.image.best_url().endswith(doc.image.filename)
assert doc.image.best_url(200).endswith(doc.image.filename)
assert doc.image.best_url(150).endswith(doc.image.filename)
assert doc.image.best_url(100).endswith(doc.image.thumbnail(100))
assert doc.image.best_url(90).endswith(doc.image.thumbnail(100))
assert doc.image.best_url(30).endswith(doc.image.thumbnail(32))
# Call as shortcut for best_url()
assert doc.image().endswith(doc.image.filename)
assert doc.image(200).endswith(doc.image.filename)
assert doc.image(150).endswith(doc.image.filename)
assert doc.image(100).endswith(doc.image.thumbnail(100))
# Save an optionnal bbox for thumbnails cropping
bbox = (10, 10, 100, 100)
with open(some_image, 'rb') as f:
doc.file.save(f, 'test.png', bbox=bbox)
API Reference¶
If you are looking for information on a specific function, class or method, this part of the documentation is for you.
API¶
Core¶
File types¶
This module handle image operations (thumbnailing, resizing...)
Backends¶
-
class
flask_fs.backends.
BaseBackend
(name, config)[source]¶ Abstract class to implement backend.
-
open
(filename, *args, **kwargs)[source]¶ Open a file given its filename relative to the storage root
-
save
(file_or_wfs, filename, overwrite=False)[source]¶ Save a file-like object or a werkzeug.FileStorage with the specified filename.
Parameters: - storage – The file or the storage to be saved.
- filename – The destination in the storage.
- overwrite – if False, raise an exception if file exists in storage
Raises: FileExists – when file exists and overwrite is False
-
Mongo¶
Errors¶
These are all errors used accross this extensions.
This exception is raised when trying to upload an unauthorized file type.
Internals¶
These are internal classes or helpers. Most of the time you shouldn’t have to deal directly with them.
Additional Notes¶
Contributing¶
Flask-FS is open-source and very open to contributions.
Submitting issues¶
Issues are contributions in a way so don’t hesitate to submit reports on the official bugtracker.
Provide as much informations as possible to specify the issues:
- the flask-fs version used
- a stacktrace
- installed applications list
- a code sample to reproduce the issue
- ...
Submitting patches (bugfix, features, ...)¶
If you want to contribute some code:
- fork the official Flask-FS repository
- create a branch with an explicit name (like
my-new-feature
orissue-XX
) - do your work in it
- rebase it on the master branch from the official repository (cleanup your history by performing an interactive rebase)
- submit your pull-request
There are some rules to follow:
- your contribution should be documented (if needed)
- your contribution should be tested and the test suite should pass successfully
- your code should be mostly PEP8 compatible with a 120 characters line length
- your contribution should support both Python 2 and 3 (use
tox
to test)
You need to install some dependencies to develop on Flask-FS:
$ pip install -e .[dev]
An Invoke tasks.py
is provided to simplify the common tasks:
$ inv -l
Available tasks:
all Run tests, reports and packaging
clean Cleanup all build artifacts
cover Run tests suite with coverage
dist Package for distribution
doc Build the documentation
qa Run a quality report
start Start the middlewares (docker)
stop Stop the middlewares (docker)
test Run tests suite
tox Run tests against Python versions
You can launch invoke without any parameters, it will:
- start
docker
middlewares containers (ensure docker and docker-compose are installed) - execute tox to run tests on all supported Python version
- build the documentation
- execute flake8 quality report
- build a distributable wheel
Or you can execute any task on demand. By exemple, to only run tests in the current Python environment and a quality report:
$ inv test qa
Changelog¶
0.4.1 (2017-06-24)¶
- Fix broken packaging for Python 2.7
0.4.0 (2017-06-24)¶
- Added backend level configuration
FS_{BACKEND_NAME}_{KEY}
- Improved backend documentation
- Use setuptools entry points to register backends.
- Added NONE extensions specification
- Added list_files to Storage to list the current bucket files
- Image optimization preserve file type as much as possible
- Ensure images are not overwritted before rerendering
0.3.0 (2017-03-05)¶
- Switch to pytest
ImageField
optimization/compression. Resized images are now compressed. Default image can also be optimized on upload withFS_IMAGES_OPTIMIZE = True
or by specifying optimize=True as field parameter.ImageField
has now the ability to rerender images with thererender()
method.
0.2.1 (2017-01-17)¶
- Expose Python 3 compatibility
0.2.0 (2016-10-11)¶
- Proper github publication
- Initial S3, GridFS and Swift backend implementations
- Python 3 fixes
0.1 (2015-04-07)¶
- Initial release