@@ -94,7 +94,7 @@ The *Engine API syncronization node* always only stores the valid (i.e. actually
This top-down synchronization process of posting any incoming playlogs at the *Engine Node* also to the *Synchronization Node* can be called **Active Sync**. This **Active Sync**
doesn't work in every scenario, as there might be the case, that the *Synchronization Node* is not available e.g. due to network outage, maintenance etc. In this situation the playlog
obviously can not be synced. That means the local playlog at the *Engine Node* is marked as "not synced".
obviously can not be synced. That means the local playlog at the *Engine Node* is marked as "not synced".
##### Passive Sync
...
...
@@ -213,9 +213,11 @@ sync_step_sleep=2
To run the API in an local development server execute:
```bash
./run.sh api-dev
./run.sh dev
```
This command implicitely activates the virtual environment before starting the API.
For convenience running a plain `./run.sh` also starts the development server.
In development mode Engine uses the default [Flask](https://palletsprojects.com/p/flask/) web server.
...
...
@@ -238,9 +240,9 @@ For production Engine API defaults to using the WSGI HTTP Server [`Gunicorn`](ht
You might also want to pair Gunicorn with some proxy server, such as Nginx.
> Although there are many HTTP proxies available, we strongly advise that you use Nginx. If you choose another proxy
server you need to make sure that it buffers slow clients when you use default Gunicorn workers. Without this buffering
Gunicorn will be easily susceptible to denial-of-service attacks. You can use Hey to check if your proxy is behaving properly.
> Although there are many HTTP proxies available, we strongly advise that you use Nginx. If you choose another proxy
server you need to make sure that it buffers slow clients when you use default Gunicorn workers. Without this buffering
Gunicorn will be easily susceptible to denial-of-service attacks. You can use Hey to check if your proxy is behaving properly.
