[jgarber]I can see it's PHP and uses MySQL, but it's unclear (to me, at least) which versions of each and how someone might get up-and-running to contribute from a fresh clone of the repository.
gRegor[jgarber], funny you mention it, I was looking to try installing to work on the moderation idea and wanted to update the readme with steps. Haven't yet, but I suspect PHP74 or later should work well since it's Slim4. It looks like you can run the schema.sql to set up the db tables.
LoqiSlim is a lightweight PHP framework for developing web applications and is used by several IndieWeb services and projects https://indieweb.org/Slim
rubenwardy<[social]> BTW, I deeply enjoy your stats page and it is close to what I’ve been wanting to so for year with my blog. Finally getting to updating the code I’m hoping will unlock taking that step for me.
barnaby, oodani, balintm and rolle joined the channel
[tantek]If you find yourself reinventing a subset of HTML as an abstraction in your application internals, you're likely making a mistake. Just directly use HTML.
[snarfed]"Any sufficiently complicated C or Fortran program contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp." – Philip Greenspun
[tantek][snarfed] I was thinking of all the mid-2000s backend code that created baroque XML as an intermediary instead of HTML, and these days baroque JSON as an intermediary instead of HTML
[tantek]Before of course, shipping off that baroque intermediary to some sort of custom template processing code that mixes in possibly "standard" template language to generate actual HTML+CSS etc
[morganm]A little over a month ago I gave this presentation to LinuxFest Northwest about web components. I've showed this to a few people and feel good about it and wanted to share it here in case it interests anyone
rosipovokay I might be dumb but I'm having a hard time understanding webmention.io vs brid.gy. So I used bridgy to get webmentions from non-webmention supporting sites, but what does webmention.io do?
[jgarber]Aside from the issues on the repo, it wasn’t clear how active the project is (aside from being deployed) or what kinds of contributions were most desired.
[jgarber]Or, rather, it’s not clear how to contribute. So, one starting point I’m interested in is making it easier for folks to run the thing locally so that they may more meaningfully contribute.
[jgarber]If that’d be welcome, of course. Not my project and I definitely don’t want to create more work for Aaron (since he owns it) or anyone else who may be managing the repo.
perryflynnwould be great to have docker support. I did that for micropublish.net as well, since this is a ruby app and it's versioning/dependency pain without docker.
perryflynnnono, it is deployed (as far as I know to heroku without docker and I added as a contribution (I am not the maintainer) dockerfile and docker-compose for local development.
gRegorHm, might need some direction on how to get the user signed in on *.indieweb.org. Meetable looks like it's using Laravel classes to handle that. IndieNews is on Slim Framework, though.
[tantek][jgarber] re contributions to IndieNews, I believe aaronpk has explicitly invited contributions to IndieNews in #indieweb-meta discussions in the past few weeks / months
[tantek]Before redesigning how it's deployed (which feels like rock shuffling a bit?) I'd think it might be better to document how it's currently tested & deployed, and then move onto triaging issues / user requests to focus on user-centric priorities first, tech debt and other cleanup second
[tantek]tbc I’m not saying ignore tech debt (or cleanup opportunities) but rather file them as issues to be triaged with everything else, or at least as a method of procrastinating them in deference to direct user issues
Loqitest in production is (AKA testing in production) deploying code changes to a web site or service typically visible to the public as part of checking to see if the code changes function as expected, and is practiced by some IndieWeb creators especially with their own projects as a form of eating their own cooking, often before publishing code changes to an open source repository https://indieweb.org/test_in_production