There is a huge demand for Pi clones in the Industrial segment. Check RevolutionPi.com. $200 for a single Pi is cheap, the equivalent Intel Box costs close to $2000, yes 10x. It's even difficult to get decent number of Industrial Pis on time.
This is exactly what we are building at TinyFunction.com Just write your function code in Javascript or Python in the browser and click deploy to get a URL. Take a look at https://TinyFunction.com
> Perhaps the issue is not the writing of the YAML, but the need to have a good understanding of all the resources/primatives in order to get things glued together.
This and the fear of making a mistake with the most important configuration file of the application.
Why not lock the core libs like Map.prototpy Array.prototype ? Can't we have sandbox like environment (which is not default but which can be enabled on application basis). Java Applets which run inside the browser had this kind of sandbox restritions.
I wonder why is it difficult to add an extra password on top of the access key.
What I mean is you can have another password or hash (separate to normal auth pass) which is only used to encrypt at browser and decrypt at the time of usage(through env load packages or your custom doppler command. This extra password is never sent or stored at doppler server.
For this beta version there is a single AWS Lambda executer function, which interprets function scripts on every request. All the function info is stored in Redis.