It was along the lines of, “How do you reach your apps/services outside your LAN?” I doubt anyone forwarding 443 for their proxy selected ‘forwarded ports’, but now you have me second guessing myself…

There is at least one workaround, if you don’t mind being a bit flexible.

GitHub lets users add multiple email addresses to their accounts and assign them as notification recipients. I’ve added a Kill-the-Newsletter (not affiliated) email to my account, and then use custom routing to route all emails for orgs I’m a part of to my email address - and everything else to Kill-the-Newsletter.

With this setup, all notifications related to orgs I specify come to my primary email address, anything else by default hits the RSS feed from Kill-the-Newsletter and keeps my inbox from getting slammed when a particular issue/etc. has a ton of activity.

I’m working on them - hopefully next!

Good call-out. The directory pulls the prominent language from each project’s repo, which is JavaScript for Mailcow.

I should update the dataset to grab any languages above a certain % threshold (25%?) to prevent instances like this where something might fall through the cracks.

I also maintain a language filter over at selfh.st/apps that can be used to identify PHP-heavy platforms:

https://selfh.st/apps/?language=PHP

Thanks for always posting it in my absence!