A django-based web receiver for Scrup which stores screencaptures on S3.
Project description
A django-based web receiver for Scrup which stores screencaptures on S3.
Features
Receives POST’ed images from scrup and uploads them to S3, and returns a valid URL for the image.
There are a few things on the roadmap:
Giving some consideration to security matters – right now it’s either HTTPS or nothing.
Exception handling.
Thumbnail generation and storage on S3
A web-based timeline showing your history of screenshot uploads so you can easily find an old screenshot you’ve uploaded.
Requirements
Installation
Getting django-scrup can be as easy as:
$ pip install django-scrup
in your favorite shell.
If you prefer to pull down and install the package yourself, you can always download or checkout the latest release and install via the usual python setup.py install.
Configuration and Usage
First, add 'scrup' to your INSTALLED_APPS. Don’t forget to ./manage.py syncdb!
You’ll also need to define a few values in your settings.py:
- SCRUP_AWS_ACCESS_KEY
Your AWS access key.
- SCRUP_AWS_SECRET_KEY
Your AWS secret key.
- SCRUP_AWS_BUCKET
The bucket in which django-scrup should store the uploaded screenshots. This must be a bucket which is writeable by the AWS user identified by the above credentials. This bucket should be solely devoted to the use of django-scrup, as the app will likely barf if it tries to upload a file with the same name as an existing file. By default, the uploaded files are stored in the root of the bucket, unless SCRUP_AWS_PREFIX is specified.
- SCRUP_AWS_PREFIX
Optional. A relative pathname to a folder within the bucket. If this value is specified, uploads will be copied to http://yourbucket.s3.amazonaws.com/<SCRUP_AWS_PREFIX>
- SCRUP_AWS_CNAME
Optional. A boolean value indicating whether to use the bucketname as the domain of the returned screenshot URL. If you’ve created a CNAME for your bucket, set this to True and the returned URLs will be of the form http://<BUCKETNAME>/foo vs. http://<BUCKETNAME>.s3.amazonaws.com/foo.
Next, make sure to import django-scrup’s urls. A line like the following in your urls.py should do the trick:
(r'^scrup/', include('scrup.urls')),
Finally, plug the URL into Scrup’s configuration. Obviously, this depends on your server’s domain and how you’ve chosen to setup django-scrup’s urls. By default, django-scrup accepts uploads at upload/<FILENAME>, where <FILENAME> is optional. Here’s an example of the default URL scheme for mydomain.com:
http://mydomain.com/scrup/upload/{filename}
License
django-scrup is made available under the terms of the new BSD license. For the full legal text, please consult the LICENSE.txt file included in the root of the source tree.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file django-scrup-0.1.tar.gz
.
File metadata
- Download URL: django-scrup-0.1.tar.gz
- Upload date:
- Size: 4.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 9b4ba2b00bddc85c96bc3ccd952817a8f78ca3639818132b97f9daaa525612bf |
|
MD5 | 5e634fc66faffb44800eab0f45de71e9 |
|
BLAKE2b-256 | 7cc7e5be1b5f07fb49826c1ecbc055bb033282633c52b1b333d941713a54142e |
File details
Details for the file django_scrup-0.1-py2.6.egg
.
File metadata
- Download URL: django_scrup-0.1-py2.6.egg
- Upload date:
- Size: 9.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 315194da111bdf57e3dc0767dc7c3043e3101b6dbcf4cb8fdc64cc1cb1e2985d |
|
MD5 | 57fd6ae4937098f678be0b06a77fb467 |
|
BLAKE2b-256 | be8f7490c77dccfb3c567025520b6a8b3f067027507078811297df0c920560b1 |