TJ

Possibly, I'm not a huge fan of that style personally since we already have stage-level overrides in `up.json`, `profile` could maybe be overridden per-stage there too. It wouldn't help the...

yeah potentially, but honestly there's not enough money in this to start adding other providers anyway :D

@Khareta if you don't have permissions for `/usr/local/bin` you could try specifying a different location with `$ curl -sf https://up.apex.sh/install | BINDIR=/path/to/other/dir sh`

Also relevant is the server timing api stuff which would let us display traces in the dev console https://blog.chromium.org/2018/02/chrome-65-beta-css-paint-api-and.html?m=1

Ahhh yea the default is `nodejs10.x` now, but looks like that'll need an update soon if they phase out `nodejs10.x` for `nodejs12.x`

Possibly! it could be a bit error-prone, if you didn't add some kind of secret/auth then anyone could hit that same end-point and trigger potentially expensive work. That's my main...

Hmm maybe: ```json { "schedules": [ { "rate": "5m", "method": "POST", "url": "/whatever", "header": { "X-Secret": "whatever" }, "body": "string or object for json?" } ] } ``` We'd need...

@kaihendry does it help if it's scheduled HTTP vs schedule Lambda? I think for now, at least until this project supersedes apex(1), it might be out of scope. I can't...

If / when Up supports "regular" Lambda functions I think it'll be a good to thing to add. I might combine apex(1) and up(1) eventually, but I'm not on-edge about...

Long-term I'd definitely like to replace apex(1), fewer tools would be nice! The FaaS part is a bit easier in comparison so at least that part should go quickly once...