-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Must set 'daemonUser in Linux' if daemonUser != name #193
Comments
Thanks :) This is just a config issue. You have to scope the daemonUser in Linux := "daemon-user"
daemonGroup in Linux := "daemon-group" |
Aha! I had an unscoped reference to |
Nevermind. Thinking a bit more on this, I'm not sure if the daemonUser in Debian := "deb-user"
daemonUser in RPM := "rpm-user"
daemonUser in Windows := "win-user" |
I think if we had them appropriately delegate up the chain, it would be ideal. You want the minimum amount of configuration REQUIRED with the maximum amount of flexibility. |
If I get this right val Debian = config("debian") extend Linux daemonUser in Linux := "linux-user",
// will override first one when calling debian:*
daemonUser in Debian := "deb-user" |
I use sbt-native-packager to package a Play 2.2 application as .deb for Ubuntu with Upstart. The server stuff in 0.7 is great and I’m already using it. You are solving my problems faster than I could even report them (support for daemonGroup, #178). Awesome work!
I noticed a little thing with 0.7.0-RC1: In my application
name
is different thandaemonUser
, anddaemonGroup
is again different from that. When I only havein
build.sbt
, the (empty) directories/var/log/appname
and/var/run/appname
are owned byappname:daemonGroup
instead ofdaemonUser:daemonGroup
. This leads to an additional, unwanted userappname
to be created in the postinstall script.If instead I put both
in
build.sbt
, everything to be owned by the process’ user is owned by daemonUser:daemonGroup as expected.So, a workaround is available, but it would be nicer if only
daemonUser
had to be set.The text was updated successfully, but these errors were encountered: