Change dir to app dir for Go applications

[andboson]

Go apps needs configs, templates, etc often. So we need to change dir to the application directory and run from it.

[mar0x]

You can use 'working_directory' directive for particular application. We will add it to the documentation ASAP.

[andboson]

Thanks for answer,
Another question: how to Unit will communicate with my Go app (rest-api in case)? Where can I set http-port of Go app? Like proxy-pass from nginx...

[mar0x]

unit.ListenAndServe(..) will use unix socket and shared memory segment created by Unit for communication. Actual TCP port listen, connection establishment etc. is done internally by Unit. Listen port can be (re-)configured via the control socket using JSON.

[andboson]

Hm, something wrong in my configs?

My Go app listens to 8001 port. And I`ve setup 8001 port in unit config too

$ sudo service unitd dumpconfig
The following configuration has been saved to /etc/unit/config:
{
"applications": {
"sale_go": {
"type": "go",
"user": "nobody",
"group": "nogroup",
"working_directory": "/home/drew/Work/www/app_go",
"executable": "/home/drew/Work/www/app_go/app"
}
},
"listeners": {
"*:8001": {
"application": "sale_go"
}
}
}

Logs

$ sudo tail /var/log/unitd.log
2017/09/08 09:48:05 net.Listen error: listen tcp 127.0.0.1:8001: bind: address already in use
2017/09/08 09:48:05 net.Listen error: listen tcp 127.0.0.1:8001: bind: address already in use

while
curl http://localhost:8001/ -d'{}'

[mar0x]

Looks like your go program tries to bind to 8001 port. Have you change it to use unit.ListenAndServe(...) instead of http.ListenAndServe(...) ?

[andboson]

No ) It`s my mistake. Thanks )

But what about tons of frameworks which use owns http wrappers?

[mar0x]

Working directory seems working for now. Let's discuss other frameworks separately.