wogra-ag / functionserver Goto Github PK

To make it impossible to add functions to a bot which is not under your control, the appId have to store the accessible bots for the appId. So it will be forbidden to add or update functions of other bots, which are not under your control.

localhost calls in httpGet and httpPost should be forbidden.

get a list of all functions with implementations over all bots.

to make working with the server comfortable commandline support should be provided to add, update, test or delete functions on the server.

at the moment the function server supports only ecma script 5 as runtime. to make more possible, it would be nice to support besides javascript webassembly as well.

we implemented a special service for sending mails. it will be easier to add this featrue as additional function to the javascript engine.

supports different versions of a function. reactivate old version, update automatically to new version.

at the moment only mysql or mariadb will be supported. in the future postrges would be a good alternative.

a new post rest service which combines the calls of create a new appId and assign it to a bot.

it the future it will be interesting to rpovide some statistics how often functions will be called. This could be important for billing services.

to test implementations on local devices, commandline support should be supported. So the function developer is able to test his/her code on local development machines.

if endless loops occures, the function must be shutdown, to make sure, that the server is stable.

see https://github.com/robertkrimen/otto#halting-problem for implementing this.

a timeout of 10 seconds makes sense.

at the moments the appids wiull be managed by a yaml config file. To make it easier to add appId at runtime, we have to move it to the daatabase and add new restcalls for managing this appIds.

which each push ci should run and after successfull tests a new version should be build.

a simple key value store for each bot is a simple way to store and load data for each bot.

function should be deactivated and activated without deleting it.

superuser appIds are allowed to access all bots and are able to add new appids for new bots or add new bots to existing appids.