Add API endpoint to list all tools

[hugovk]

I've created a CLI to access the API!

https://github.com/hugovk/norwegianblue

For example:

It would be useful to have an endpoint to list all the tool names, currently:

$ cat api/all-tools.json
["alpine","amazon-linux","android","bootstrap","centos","debian","django","dotnet","dotnetcore","dotnetfx","drupal","elasticsearch","elixir","fedora","filemaker","freebsd","go","godot","iphone","java","kindle","kubernetes","laravel","macos","magento","mariadb","mongodb","mssqlserver","mysql","nodejs","office","perl","php","pixel","postgresql","powershell","python","rabbitmq","rails","redis","rhel","ros","ruby","spring-framework","surface","symfony","ubuntu","wagtail","windows","windowsembedded","windowsserver"]

https://deploy-preview-273--endoflife-date.netlify.app/api/all-tools.json

Naming things is hard; I wasn't sure about the address api/all-tools.json.

What do you think?

Could also be worth thinking if the regular API should be something like /api/v1/tool/python/3.9.json and /api/v1/tool/python.json?

[captn3m0]

API versioning is something worth considering once we finalize on the API specification. Right now, it is very ad-hoc (See the keys for iPhone) and the schema is varying between tools as a result. So perhaps once we have that finalized, we could switch to /v1/ (we could perhaps redirect /api/* -> /api/v1/* as well once we have that). Will create a separate discussion for that.

Calling everything tool is also something that I'm not very happy with (it is only used in code as a result, not on the frontend), but we haven't found a better word so far. Maybe /api/all.json instead, so we avoid that whole problem (for now).

[captn3m0]

Also, love the CLI 💯, that's gonna be very helpful (especially as we finalize the API schema). Thoughts on moving it under the endoflife.date org as the "official" CLI?

[hugovk]

API versioning is something worth considering once we finalize on the API specification. Right now, it is very ad-hoc (See the keys for iPhone) and the schema is varying between tools as a result. So perhaps once we have that finalized, we could switch to /v1/ (we could perhaps redirect /api/* -> /api/v1/* as well once we have that). Will create a separate discussion for that.

👍

Calling everything tool is also something that I'm not very happy with (it is only used in code as a result, not on the frontend), but we haven't found a better word so far. Maybe /api/all.json instead, so we avoid that whole problem (for now).

Sure, renamed! There was a suggestion in #90 for "maybe also one for ALL the tools at once", which would be more "all" than this PR's list.

[hugovk]

Also, love the CLI 💯, that's gonna be very helpful (especially as we finalize the API schema). Thoughts on moving it under the endoflife.date org as the "official" CLI?

Would be happy to!

[captn3m0]

Will review this soon, I promise.

[usta]

@hugovk small suggestion :
add colorize into your install_requires and also make small changes to your src/norwegianblue/init.py :
change :

from termcolor import colored

to

from colorama import init
from termcolor import colored
init()

this will let color also works on windows systems
termcolor is really old module and doesnt support some systems so using colorama and termcolor together
will fix all problems.

[hugovk]

Good idea! I created an issue in the repo as a reminder. hugovk/norwegianblue#8

[captn3m0]

Thanks a lot, I'll file a new PR for the docs update.