Browse files


  • Loading branch information...
1 parent a65524b commit 9071cf502943c53870177472099cca04cef14e7f @hsk81 committed Jan 25, 2014
Showing with 3 additions and 6 deletions.
  1. +3 −6
@@ -49,8 +49,7 @@ You need to run *three* components to get a functional application: a *frontend*
Create `/var/www/webed` for sharing purposes (on the host machine), and give ownership to the `www-data` user and group; some GNU/Linux distributions may use `http` instead of `www-data` as the owner.
-Frontend: `ntx`
+### Frontend: `ntx`
export QUEUE=tcp:// && docker run -name ntx -t -p 8080:80 -p 9418:9418 -v /var/www/webed:/var/www/webed:rw hsk81/notex:run PING_ADDRESS=$QUEUE:7070 DATA_ADDRESS=$QUEUE:9090 $(cat
@@ -61,8 +60,7 @@ Then run the *frontend* container named `ntx` and map the internal port `80` to
The command also maps the `9418` port, which belongs to a `git-daemon`: This allows youto `clone` a particular repository from your host (if you know its randomly generated name), like `git clone git://..`.
-Queue: `qqq`
+### Queue: `qqq`
docker run -name qqq -t -p 7070:7070 -p 9090:9090 -p 7171:7171 -p 9191:9191 hsk81/notex:run ./ queue -pfa 'tcp://*:7070' -dfa 'tcp://*:9090' -pba 'tcp://*:7171' -dba 'tcp://*:9191'
@@ -73,8 +71,7 @@ As mentioned the queue offers four binding points: two for *frontend* container(
The application uses the *ping* and *data* channels for different purposes: Given a conversion job, the frontend asks the queue via a "ping" through the former channel if a worker is available, and if so it sends the corresponding data through the latter channel. The queue figures in a similar way which backend converter is idle and chooses it for the job.
-Backend: `spx-1`
+### Backend: `spx-1`
export QUEUE=tcp:// && docker run -name spx-1 -t -v /var/www/webed:/var/www/webed:rw hsk81/notex:run ./ converter -p $QUEUE:7171 -d $QUEUE:9191 --worker-threads 2

0 comments on commit 9071cf5

Please sign in to comment.