To configure destinations, create a configuration file according to ./docs/source/man_sbws.ini.rst (or /docs/source/man_sbws.ini.rst or :doc:`man_sbws.ini` or man sbws.ini)
{{{
To configure destinations, create a configuration file according to ./docs/source/man_sbws.ini.rst (or /docs/source/man_sbws.ini.rst or :doc:man_sbws.ini or man sbws.ini)
}}}
line 5) redirect http://keepachangelog.com/en/1.0.0/ - permanently to https://keepachangelog.com/en/1.0.0/
Which we should change to https, will open other ticket for that.
Or :
(line 88) broken https://docs.python-requests.org/ - HTTPSConnectionPool(host='docs.python-requests.org', port=443): Max retries exceeded with url: / (Caused by SSLError(CertificateError("hostname 'docs.python-requests.org' doesn't match either of '*.readthedocs.org', 'readthedocs.org'",),))
I tried to cover all the possible ways one could read the documentation from, which are:
rst source files (no Internet, not build documentation): /docs/source/X.rst
Github: interpret rst, but not Sphinx references: <X.html>_
rtfd and locally build documentation: interpret Sphinx references and rst: :doc:X
3 is not needed and i need to fix 2
All the other sphinx directives, would be also broken when reading the docs in Github, like :term:scanner (interpreted as docs/glossary.html#term-scanner in rtfd)
If we want that the docs can be read in Github, i'd need to stop using Sphinx directives and remove all of them.
Maybe there should be warning instead saying to look the documentation in rtfd?.
There's the Debian package sbws-doc, which includes the html pages generated by Sphinx, in which the directives are correctly interpreted.