This repository hosts the source code of the PlayCloud platform, an experimental testbed to evaluate different erasure-coding libraries. Full paper here: http://link.springer.com/chapter/10.1007/978-3-319-39577-7_13 Feel free to contact the authors for a pre-print copy of the paper.
- docker [https://docs.docker.com/engine/quickstart/]
- docker-compose [https://docs.docker.com/compose/install/]
- docker-machine [https://docs.docker.com/machine/]
$docker-machine create -d virtualbox playcloud
$docker-machine env playcloud
$eval $(docker-machine env playcloud)
$git clone https://github.com/safecloud-project/playcloud.git
$cd playcloud
$docker-compose build
$docker-compose up -d
$echo "hello" > my-file.txt
$curl -v -X PUT `docker-machine ip playcloud`:3000/my-file.txt -T my-file.txt
$curl -v -X GET `docker-machine ip playcloud`:3000/my-file.txt -o my-file.txtPlaycloud is split in 3 components:
- proxy - A web server taking requests on port 3000
- encoder-decoder - A enconding/decoding component
- storage - A database to saved the encoded data
In order to start the server, run the following command in your terminal:
docker-compose build
docker-compose up (or -d to run in detach)
This command will launch three containers. One named proxy, containing the web application accepting HTTP requests on port 3000, a second one named coder in charge of encoding/decoding and a last one name redis for storage.
The server currently accepts 2 types of requests.
Retrieves a file from the storage component.
curl -X GET my-server:3000/my-file.txt -o my-file.txtSends a file to the storage component.
curl -X PUT my-server:3000/my-file.txt -T my-file.txtThe encoder/decoder's configuration can be overloaded by environment variables. These values can be added/modified in the erasure.env file which is loaded when starting the server up.
An export of the main branch (git rev: 49f27af64c1bd69be06b96d4e9d3ba0bec516e12 ).