Robin Speekenbrink

Jeff, Haven't been able to get more debug info than this, but you're right that the newrelic agent does launch an extra process which pushes the gathered data to NR...

I've given up on dokku+NR... The launching of the extra daemon by NR inside the container (since that extra daemon will push the data to NR periodically) crashes the container...

I haven't seen an updated solution just yet @mattions maybe @progrium has news?

I fully agree on inclusion into the app manifest. I was just building upon the current CHECKS implementation and seeing where it could go. I couldn't find anything in Heroku...

I've been looking into the app.json specs and they have no mentioning on the actual status checks. I'll post and issue there to gauge their interest...

Understood. It has indeed been too quiet (atleast on the app.json repo) You mentioned the move to support multiple schedulers... Is there a roadmap for the entirety of dokku available...

@josegonzalez this would entail a pretty big rewrite to incorporate any form of 'release phase' checks. Also I haven't yet found the non-web spec in the wercker.yml (as the wercker.yml...

@josegonzalez that looks **really** nice! It's not overly hard to read, it corresponds to a leading solution in naming, spec and does provide a way forward! Awesome!

- Version of dokku you use: 0.4.13 - Non-core plugins in use: - dokku-letsencrypt - dokku-redis - dokku-mysql (and dokku-mariadb) - dokku-hostkeys (and dokku-deploymentkeys) - Company Name: Kingsquare - Size...

@Jonatanmdez Couldn't the use of the global dokku config solve this issue for you? `dokku config:set --global [email protected]` That way the e-mailaddress used is non unique and doesn't that help...