{"action":"opened","issue":{"url":"https://api.github.com/repos/garywiz/chaperone/issues/2","labels_url":"https://api.github.com/repos/garywiz/chaperone/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/garywiz/chaperone/issues/2/comments","events_url":"https://api.github.com/repos/garywiz/chaperone/issues/2/events","html_url":"https://github.com/garywiz/chaperone/issues/2","id":98018557,"number":2,"title":"How should I call a runtime startup script?","user":{"login":"mc0e","id":1965393,"avatar_url":"https://avatars.githubusercontent.com/u/1965393?v=3","gravatar_id":"","url":"https://api.github.com/users/mc0e","html_url":"https://github.com/mc0e","followers_url":"https://api.github.com/users/mc0e/followers","following_url":"https://api.github.com/users/mc0e/following{/other_user}","gists_url":"https://api.github.com/users/mc0e/gists{/gist_id}","starred_url":"https://api.github.com/users/mc0e/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mc0e/subscriptions","organizations_url":"https://api.github.com/users/mc0e/orgs","repos_url":"https://api.github.com/users/mc0e/repos","events_url":"https://api.github.com/users/mc0e/events{/privacy}","received_events_url":"https://api.github.com/users/mc0e/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-07-29T20:02:47Z","updated_at":"2015-07-29T20:02:47Z","closed_at":null,"body":"It's common practice in docker containers to have some script that gets run at run time to do things like take values from environment values and construct the odd config file with them before the main daemon process(es) get run.  This commonly gets shoe-horned into the CMD or ENTRYPOINT directive.\r\n\r\nIt seems in keeping with the philosophy of chaperone that this should probably hang off the chaperone config, and also I suspect not doing it that way would mean that the wrong process would be PID 1, and responsible for zombies.  I'm still just finding my way here, but I'm not seeing a really elegant way to do it with chaperone.  What am I missing?\r\n\r\nMaybe I could create a one-shot service, and set up some before/after rules.  Is there a better way?"}}