TJ
TJ
Oh interesting, yeah I would definitely suspect env vars, nothing else in the function config is of a variable size really. In any case 5k seems really small to me...
I think you should be ok deploying after `up upgrade -t 0.7.3` to grab an older version of Up. In a more recent version I changed it from loading at...
Damn, sorry about that! I'll keep bugging them about raising that limit
sweettt, I'll try to look into all these new announcements
Looks like a big nope for now — https://twitter.com/tjholowaychuk/status/1069629064691023872 You have to set runtime to "provided" in order to use one in a layer, at which point you lose the...
ahhh the CI must have fooled the isatty check https://github.com/apex/up/blob/master/internal/cli/deploy/deploy.go#L35 wonder if that's really a good thing on their part, if there's no interactive stdin
Right now it has a select input for the AWS profile, so it bails on helping create up.json if there's no creds. Ideally it'd help walk through adding a profile...
Currently it's only possible to use the Node runtimes, just due to how an internal shim works, but I was planning on adding a Python one (issue #671). It passes...
Currently stuck with python3.4 I believe, if you define `proxy.command` in up.json to `python3 app.py` I think that should do the trick. Thought about making that the default but I'm...
Oh I missed that, try removing the `runtime` in up.json. I'll clarify in the docs but it has to be one of the `node*` runtimes currently (hard to explain why...