#sebselYeah I notice I don't use any UI from the Kirby CMS now, so in a way I'm not really using the Kirby CMS, only the Kirby Framework. And it's just not that good at being a framework.
#schmartyaaronpk: (and other folks that use framework-y PHP). after some success with a simple webmention.io receiver in PHP, i am interested in doing more PHP stuff w/ my site. i see that many of your PHP projects are either Laravel- or Slim-based. Do you have any current feelings about these?
#aaronpkLaravel is a more complete framework, it includes a database ORM, caching, a job queue, a template system, etc etc. Slim is just the router part so you'll need to put a lot more pieces together yourself with that
#aaronpkIf a more DIY approach is your thing, Slim might be better. But also check out Plates and Route from the php league
#schmartythe current project(s) are for little micro-service-like webhooks like the one i just made for receiving webmention.io data.
#schmartyooh, i had not heard of Plates and Route before, will check those out.
#schmartymy bigger project right now is a webhook that gets notified of new git commits on my site repo, pulls down those commits, and builds the site.
#schmartyso a job system for those bits sounds good
#aaronpkCourse if you want a minimal job queue, check out my Caterpillar repo ;-)
#schmartyi also want to add in intermediate steps like fetching /link-preview content for posts that are in-reply-to other posts on the web, which should also be job-y.
#schmartyhaha, I have my eye on Caterpillar for sure. :}
#aaronpkI use the small building blocks for smaller utilities, like my latest Watchtower which doesn't even have a UI
#schmartyah, and Compass runs on Lumen, which is a more minimalist framework from Laravel?
#sebselI believe the goal of Lumen is to be a small variant of Laravel. Any Lumen application can be used with a Laravel vendor folder and still run, so the upgrade is very easy
#aaronpkI think Lumen is deprecated. They rolled most of it into Laravel.
#aaronpkIt started as a fork of Laravel meant for APIs
#schmartyoh, right. i think i remember reading about Lumen being deprecated. :|
#ZegnatI am with aaronpk on the “use [framework] when I'm making something that will use at least a few of its major features”. Most of the time I find I don’t need a full framework and much rather pull in just the parts I do need.
#schmartyhas deja vu about intending to pick up a PHP framework :}
#ZegnatSlim is pretty good for normalising a router with PSR-7 compatible HTTP Request and Response objects. Which is pretty nice, and I find it is the basis I want for most sites.
#sebselI got my homepage in Laravel's Blade-template now, just to get a feel for it.
#sebselTurns out there is a loooot of logic in my templates that shouldn't be there.
#ZegnatFor licit.li I just pull the parts I wanted in separately: FastRoute for routing (which is the code that is used by several frameworks anyway) and Nyholm/psr7 for the HTTP objects.
#sebselThe h-card in the header is one big pile of if-statements to apply mf2-fields when needed :P
#aaronpkgrantcodes++ thx for the github isseus, all fixed! (I hope)
#Loqigrantcodes has 4 karma in this channel (6 overall)
#aaronpkyea /feed and /feed/ are different and I won't make any assumptions about that
#ZegnatI see too many people making assumptions about that. Those trailing slashes aren’t optional, but because of years of URL rewriting some people treat them as if they are
#ZegnatI was unhappy with several ways Kirby does routing and treats HTTP requests
#aaronpkfile a bug? you can always cite the google SEO reason for not wanting to serve duplicate content at a bunch of URLs
#sknebelsebsel was as well, if I remember the later stages of the private webmention experiments
#sebselI broke so many things while trying to get webmentions to work properly.
snarfed joined the channel
#Zegnatsebsel has a bug open on the current in-development upcoming Kirby about how they do not map GET and HEAD requests to the same thing. I have one about how they are limiting HTTP methods to a small predefined list and uppercasing the methods.
#sebselyeah, that was what I meant with "it's just not really good at being a framework".
#ZegnatMy issue titles “Treat methods in accordance with the HTTP spec” is labelled as an enhancement, not a bug ?