Satya van Heummen

Thanks for your quick response. However this event only seems to be emitted after the connection becoming online again. I need a callback while being offline.

I understand. But my code is waiting for a callback to continue, so it breaks the code. With Ground, when offline, method calls are being saved to be resumed later....

This is all the reason I get. No it's a new app. And it's the first time deploying with Mup 1.5. Started on a fresh DO VPS...

``` mup status => Servers - 167.71.7.108: Ubuntu 18.04 => Docker Status - 167.71.7.108: 19.03.11 Running => Meteor Status - scanapp - 167.71.7.108: restarting Created at 2020-06-03T19:16:54.411003605Z Restarted 12 times...

Btw, I'm running Meteor 1.10.2

I figured it out. If there's a single error thrown somewhere in the code during server startup, Mup will abort - even when that error is within try/catch. That's quite...

I run into this error constantly, really annoying. Datatables seems to have a nag for mutating its props for no apparent reason

This is indeed not working at all. If you try to do this: ``` Template.example2.viewmodel({ share: 'clock' onCreated: function() { console.log(this.clock); } }); ``` it will throw an error saying...