No sudo when using upstart

[gerhard]

No sudo when using upstart

[gerhard]

Won't make it into this release...

[haad]

You can make upstart listen to user commands, too. E.g. on one customer install I made upstart take user script config from .init.d and user was able to start/stop his upstart jobs processes.

If you add this to /etc/dbus-1/system.d/Upstart.conf, everyone in railsapp group will be able to send commands to upstart.

  <policy group="railsapp">
    <allow send_destination="com.ubuntu.Upstart"
           send_interface="org.freedesktop.DBus.Properties" />
    <allow send_destination="com.ubuntu.Upstart"
           send_interface="com.ubuntu.Upstart0_6" />
    <allow send_destination="com.ubuntu.Upstart"
           send_interface="com.ubuntu.Upstart0_6.Job" />
    <allow send_destination="com.ubuntu.Upstart"
           send_interface="com.ubuntu.Upstart0_6.Instance" />
  </policy>

Upstart init configuration scripts are then placed at ~/.init/ directory.

[gerhard]

Very nice find ; ). I will look into this some more - thanks!

[gerhard]

Now that most people should have migrated to 12.04, this might be helpful: Upstart Load User Jobs & Upstart User Job

[alexcurtis]

Is there any way around the sudo upstart issue? -- Could we have a separate 'runas' user for foreman so the application can still be sandboxed? At the moment we seem to have a single user for both delivery and running the application.

[gerhard]

@alexcurtis this has been open for far too long, I will look into this today and get back to you with a temporary solution.

[alexcurtis]

@gerhard thanks :-)

[gerhard]

@alexcurtis see #59, in particular the last commit.

[gerhard]

The deliver successor (yes, it is happening!) will leverage runit most likely which has full support for user jobs. Closing this as it's outside the scope of the upcoming final release.