2017-06-21 15:09:49 +02:00
|
|
|
Testing Flatisfy using Docker
|
|
|
|
=============================
|
|
|
|
|
|
|
|
A basic `Dockerfile` is available for rapid testing. It is still really hacky
|
|
|
|
and should not be used in production.
|
|
|
|
|
|
|
|
|
2017-11-26 21:53:59 +01:00
|
|
|
1\. First, build the docker image:
|
2017-06-21 15:09:49 +02:00
|
|
|
|
|
|
|
```
|
|
|
|
cd docker
|
2017-11-26 21:53:59 +01:00
|
|
|
docker build -t phyks/flatisfy .
|
2017-06-21 15:09:49 +02:00
|
|
|
```
|
|
|
|
|
2017-11-26 21:53:59 +01:00
|
|
|
2\. Then, create some folder to store your Flatisfy data in a permanent way (it
|
2017-06-21 15:09:49 +02:00
|
|
|
will be mount as a Docker volume in next steps), and initialize an empty
|
|
|
|
config:
|
|
|
|
|
|
|
|
```
|
|
|
|
mkdir flatisfy
|
|
|
|
cd flatisfy
|
|
|
|
FLATISFY_VOLUME=$(pwd)
|
2017-11-26 21:53:59 +01:00
|
|
|
docker run -P -v $FLATISFY_VOLUME:/flatisfy -p 8080:8080 phyks/flatisfy sh -c "cd /home/user/app && python -m flatisfy init-config > /flatisfy/config.json"
|
2017-06-21 15:09:49 +02:00
|
|
|
```
|
|
|
|
|
|
|
|
|
2017-11-26 21:53:59 +01:00
|
|
|
3\. Then, edit the generated `config.json` file according to your needs. See
|
2017-06-21 15:09:49 +02:00
|
|
|
[0.getting_started.md](0.getting_started.md) for more infos on the
|
|
|
|
configuration file format.
|
|
|
|
|
|
|
|
|
2017-11-26 21:53:59 +01:00
|
|
|
4\. Finally, run the docker image to fetch flats and serve the web UI:
|
2017-06-21 15:09:49 +02:00
|
|
|
|
|
|
|
```
|
2017-11-26 21:53:59 +01:00
|
|
|
docker run -P -v $FLATISFY_VOLUME:/flatisfy -p 8080:8080 phyks/flatisfy
|
2017-06-21 15:09:49 +02:00
|
|
|
```
|
|
|
|
|
|
|
|
Your Flatisfy instance is now available at `localhost:8080`!
|