I would appricate it if Honk 0.9.8 makes it in the 7.2 ports -release but I think it will not as it is now. As we Honked today, I try to explain how I would change the diff.
Basically, I find it good that you care of not experienced users but this information is not required that the port works or is useable and it makes more work to have informations on various places (that means not, that you should remove it, I just would implement it in another way). I would write it in the following way. Honk requires relayd(8) (because it is already in the base system) as TLS endpoint. That means you need a SSL certificate which you can obtain using acme-client(1) and a server section in httpd.conf(8) (maybe including a 302 redirect from HTTP to HTTPS). - for experienced users you have nothing more to explain and it keeps discussions about how to make this and that away from the mailing list. If someone uses software x they have to self find out how (thats why the information that relayd is in the base system). If you are new to running your own web services or to Honk, there is a detailed writeup at the maintainer blog ... - your URL, there you can explain all details (from DNS - to cron) and also show how to setup the dev version of Honk to help tedu test things. In your blog you could spread the word about the OS, Honk and the fedi. Beside of that, in the examples directory of Honk you find example configuration files. - just ask tedu to add your acme-client.conf, httpd.conf and relayd.conf file which you also could use to decument / explain things. - then you could add the 4 lines of the relayd.conf file which are related to Honk, the init and the upgrade section. Just a idea and just my 2 cents, the committers decide. BTW the diff still works as it should, I setup Honk again on a clean install using 7.2 GENERIC.MP#734 amd64 from monday this week. Regards, Christoph P. S. sorry if the format is not as it should be, I try to use Mutt.
