d4rkstar commented on issue #98: URL: https://github.com/apache/openserverless/issues/98#issuecomment-2699018152
Hello @AntonioVergari, good! However for now, i would leave out the examples, which we will focus on in a separate issue. For this issue the idea is to generate the documentation automatically using a script that produces the documentation Markdown pages for each language. The script can be used from a task inside the openserverless-site [Taskfile.yml](https://github.com/apache/openserverless-site/blob/main/Taskfile.yaml). This task could be called `import-runtimes`. So we can import tools, task and runtimes! This can be done by parsing the openserverless-task [runtime.json file](https://github.com/apache/openserverless-task/blob/main/runtimes.json) and then, for each language/version, the relative dependencies file (requirements.txt, package.json, composer.json etc. etc.) from the openserverless-runtime repository. The script can then be limited to the languages of the openserverless "apache" runtime images (If you take a look inside the runtime.json file, you can notice that some runtime images are "apache" and other are "openwhisk"). This way, it is possible to make a detailed map of each runtime, with the versions, the libraries included with their versions etc. etc. A typical runtime page can be organized this way: - LANGUAGE (example nodejs) - VERSION (default true | false) - INCLUDED LIBRARIES (a table with these columns: library name, version, url) If I could choose an order, I would start with python and nodejs and then move on to the other languages. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
