#known 2021-07-06
2021-07-06 UTC
[KevinMarks], [snarfed], [tantek], [fluffy], [pfefferle], [Ana_Rodrigues], jamietanna1, [Murray], [manton], [aciccarello] and cambridgeport90 joined the channel
# 
cambridgeport90 it's amazing what a trip to a rainy Plymouth, NH, and a new mint-condition Latitude 5410 can bring to the table during testing. I got Known working... on IIS! See the issue about it on GitHub; at the moment, I am getting my hands dirty learning the basics of Apache directives so that I can correctly translate all of the rewrite rules to IIS XML (tried automatically importing them, but there are too many incompatibilities.) It
# cambridgeport90 does work though right now with the custom Helicon Ape module installed and registered with IIS.
# cambridgeport90 While that is nice, not everyone is going to want to pay for a custom server extension (not to mention, under most shared hosting environments, one can't manipulate the configuration of the web server itself.
# cambridgeport90 As a bonus, I also got the Twitter plugin working by doing the following: setting up the environment via cloning Known via GitHub, then running Composer on top of it, and then cloning the Twitter plugin directly into te plugins directory via GitHub as well, and running Composer Update on top of that folder. Worked just fine. Have yet to figure out what's causing the awful 500 on my prod site, but part of me almost doesn't
# cambridgeport90 care, since I can't stand Plesk anyway, and it's not the first time that Plesk and nothing else not plain IIS, Apache, Nginx, CPanel, has caused problems with sites throwing nonsensical 500 error messages that mean nothing anywhere else.
# cambridgeport90 (honestly, for anything to work right in Plesk, you have to learn an outdated format for Web applications that no one supports anymore, and they still haven't updated it.). If I make known compatible with any platform as a first class citizen, it's going to be WebDeploy/IIS.
[jacky], [Murray], [schmarty] and [tw2113_Slack_] joined the channel