Expose tags_separator config through /info API

[amadeous]

Expose the value of the configured tags_separator through the /info API endpoint.
This value can be used by clients (such as Shaarlier, see issue #55 on Shaarlier) for consistency.

[nodiscc]

Maybe https://github.com/shaarli/api-documentation/blob/master/api-documentation.md#settings should be updated as well

[amadeous]

You're right. I forgot that doc. I did the PR 38 (here) on the api-documentation repo.

Is there any reason why the api documentation is separated from the main documentation?
It would be appreciable to have both at the same location (and also to stop using aglio.js, as the last commit was in 2018.. ^^")

[nodiscc]

Is there any reason why the api documentation is separated from the main documentation? It would be appreciable to have both at the same location

I'd also prefer it to be moved to the main repo. There is no actual reason other than (I guess) being able to use the https://shaarli.github.io/api-documentation/ URL on Github pages. I think that could be worked around easily (keep https://github.com/shaarli/api-documentation an empty repository, and have Shaarli's main repository CI push to the gh-pages branch there). Or maybe just regroup it with https://shaarli.readthedocs.io/?

and also to stop using aglio.js, as the last commit was in 2018

Actually the API documentation repo has been neglected since 2020, it still uses our old Travis CI account which stopped working about a year ago. I'm not sure the documentation itself is up to date, your PR to expose tags_separator just reminded me that this repo existed. As you noticed, the documentation renderer (aglio) is also unmaintained. We should move to another generator that supports the API blueprint source format.

Thank you for pointing this out, I'll open separate issues and see what can be done.

[nodiscc]

Thank you for pointing this out, I'll open separate issues and see what can be done.

#1999