Brian LeRoux

Easy to also argue that yarn is also a non standard node practice! ;) The reason we don't add `aws-sdk` to `package.json` is that AWS Lambda Node.js runtime already has...

also lets move 'examples' under 'getting started'

the big reason is dependencies. ruby and python (and other runtimes) don't have the luxury of auto dep creation so we'd need to figure something out for that similar to...

This is an older macro (plugin) that demos adding DSN stuff w Route53 and may be helpful; generally we've found people want to use other registrars and CDNs so didn't...

OMG, this is awesome!!! I have a PACKED day but will respond in a more thoughtful later this afternoon/evening. Stoked to have your help!!!

This isn't a bug! I feel like a broken record so I'm sorry if you heard this already. Architect has three envs ALWAYS: testing, staging and production. Why? Because all...

point would be arbitrary staging envs (which means those commands should accept an arbitrary name as well) … I don't personally do this much but I do see the idea....

sorry sorry! I'm replying too quickly here. Let me try again. You can have multiple arbitrary stacks (environments) where `process.env.NODE_ENV === 'staging'` but the stack name is different. There is...

Nope, not a bug. Very deliberate. Stacks are the unit of deployment. There are three environments: `testing`, `staging` and `production`. There are no other envs…but you can have arbitrary staging...

> The list of options is endless! In all those cases those envs where `staging`. I ack that bigcos make big messes and that they have large adhoc envs without...