On 7/19/21 9:42 AM, Sarah H wrote:
so there should be inside the docroot created by collectstatic a location /docroot/archives(or hyperkitty)/api? or is there another location that this particular page should be served from? at present the hyperkitty directory there is only css, fonts, img and js dirs.
if I can find where this should be served from in the file system that'll give me some way to figure out what I'm actually looking for URL wise...
Hyperkitty is not serving a web page. HyperKitty has an API at base_url/api with a few endpoints and generates responses to various GETs and POSTs to those endpoints.
Mailman core makes calls to methods in mailman_hyperkitty/__init__.py which in turn call the HyperKitty APi and return the result.
The list_url(mlist) method is called to get the URL to the list's
archive for the List-Archive: header. It in turn does a GET for
base_url/api/mailman/urls with query fragments key=<api_key> and
mlist=<the fully qualified list name> to get the URL
The permalink(mlist, msg) method is called to get the link to where
HyperKitty will store the message for the Archived-At: header. It in
turn does a GET for base_url/api/mailman/urls with query fragments
key=<api_key>, mlist=<the fully qualified list name> and msgid=<the
message-id from the message> to get the URL
The archive_message(mlist, msg) method is called to actually archive
the message. It in turn does a PUT for base_url/api/mailman/archive with
the api_key, the fully qualified list name and the text of the message.
See https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperkit... for the full detail.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan