On Thu, Apr 23, 2015 at 4:54 AM, <
xilarra...@qdqmedia.com> wrote:
> Hi!
Hey there! :)
> [...]
>
> How does it work the deployment flow between circus, procfile and tsuru unit
> agent? Isn't clear in the docs. I deployed and application in Go but if I
> kill the app the watcher doesn't restart the application automatically, How
> can I configure that? it's implemented?
How did you deploy the application? Which platform you're using? You
need to check whether circus is actually managing the application
process, this is defined by the platform. FTR, our Go platform doesn't
use circus [1], but it should, so I will work to fix it today.
Here is the relation:
- tsuru-unit-agent is reponsible for the start-up of the unit, it does
the initial communication with tsuru (registering the unit there and
retrieving environment variables from the tsuru API), and invokes the
start script defined in the platform. Usually, the start script just
calls Circus [2], but this isn't the case for the Go platform [1]
- before calling the start script, tsuru-unit-agent reads the Procfile
and generates the circus configuration file
> Also the stdout doesn't log with app-log, is that a bug? the docs say that
> app-log captures stdout and stderr.
tsuru depends on Circus for capturing stdout and stderr, so it's
another bug in the Go platform. I'm working to fix it right now.
[1]
https://github.com/tsuru/basebuilder/blob/master/go/start
[2]
https://github.com/tsuru/basebuilder/blob/master/python/install
Thanks,
Francisco