From bf5d6a0af7344d4283e49056feb97959e6a493eb Mon Sep 17 00:00:00 2001 From: Rui Carmo Date: Sat, 26 Nov 2016 23:11:31 +0000 Subject: [PATCH 1/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 80b2092..acd84a6 100644 --- a/README.md +++ b/README.md @@ -59,7 +59,7 @@ From the bottom up: * It then looks at a `Procfile` and starts the relevant workers using [uWSGI][uwsgi] as a generic process manager * You can then remotely change application settings (`config:set`) or scale up/down worker processes (`ps:scale`) at will. -Later on, I intend to do fancier `dokku`-like stuff like reconfiguring `nginx`, but a twist I'm planning on doing is having one `piku` machine act as a build box and deploy the finished product to another. +![](img/piku.png) ## Supported Platforms From a7969a8021f74dd288e7e8b91bfc11b54643a2d4 Mon Sep 17 00:00:00 2001 From: Rui Carmo Date: Sat, 26 Nov 2016 23:13:46 +0000 Subject: [PATCH 2/2] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index acd84a6..9fc7268 100644 --- a/README.md +++ b/README.md @@ -59,6 +59,10 @@ From the bottom up: * It then looks at a `Procfile` and starts the relevant workers using [uWSGI][uwsgi] as a generic process manager * You can then remotely change application settings (`config:set`) or scale up/down worker processes (`ps:scale`) at will. +## Internals + +This is an illustrated example of how `piku` works for a Python deployment: + ![](img/piku.png) ## Supported Platforms