[19:15:45] Who/where would I ask about adding an extension to composer? [19:16:29] What do you mean by adding it to composer? [19:16:42] Generally installing extensions via composer isn't reccommended and isn't well supported [19:21:46] I mean it's been seeming to work pretty well so far; I'm building a container for mediawiki is and have been using composer for most of the non-included extension setup [19:22:18] It might work, but that still doesn't mean it's recommended nor supported :) [19:22:33] Annoyingly while simpleSamlPhp the PHP bit is on composer, the actual mediawiki extension isn't [19:23:18] So I was wondering who I'd ask about that [19:23:33] But I can always just add it's installation to the rest of the bootstrapping code I have [19:24:51] And I'm pretty sure a lot of what I'm doing is not recomended TBH [19:33:03] I guess you need to ask the maintainers to publish it [19:40:55] Just on the extension talk page then? [19:40:56] Oki [19:40:57] Thanks [19:44:25] jediminer5432 see https://phabricator.wikimedia.org/T311321 [19:52:27] Mhm it'd just be nice as I'm going to use composer to install simpleSamlPhp regardless as it's a whole lot easier than writing my own dependency management engine [19:53:52] T249573 & T250406 [19:53:52] T249573: RFC: Remove ability to install extensions and skins with Composer - https://phabricator.wikimedia.org/T249573 [19:53:53] T250406: RFC: Hybrid extension management - https://phabricator.wikimedia.org/T250406 [19:55:28] It is odd that there is a provided extensions hub but nothing to automaticly interface with it [19:55:43] provided extensions hub? [19:57:35] If you want to use composer to install MediaWiki extensions that don't have a valid composer.json file, you have to declare your own 'package repository' for each one in the repositories section of composer.local.json like this:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/7a142effd290ee8100f276ee7a3ecafec0768cce) [19:58:08] Or, use a private registry that you create yourself. [19:58:13] Oh neat thanks rundg [19:58:48] That's what I was looking to do [20:10:31] in a MediaWiki template, is there a variable that contains the namespace of wherever the template is used. like... so that you can use it in an "if" inside the template to return different results if it's used on a User: or Talk: page vs when it's used in the main namespace? [20:11:58] Yes, it's `{{NAMESPACE}}` [20:12:33] I was just thinking to myself "they will probably say it's namespace, lol" [20:12:38] Marijn[m]: ACK, thank you [20:12:53] https://www.mediawiki.org/wiki/Help:Magic_words#Namespaces [20:12:58] yea, that solves an issue a Wikipedia user asked me about [20:13:15] a template is NOT supposed to do certain things when used outside the main NS [20:13:19] thanks as well bd808 [20:26:40] "provided extensions hub?" <- I think the OP was referring to mediawiki.org listing all extensions, but there's nothing like packagist to programmatically install them. Sure you can use git, but you need a lot of custom scripting. That's why everyone uses Composer. You just specify your package requirements in a json file and do a `composer up`. The term 'hub' probably comes from Docker Hub where you do the same thing on a higher [20:26:40] level for the full app. [20:27:06] I'm not sure how git clone is a lot of custom coding ;) [20:28:03] And yes, I know how composer works [20:36:44] So, this is my partial composer.local.json file https://pastebin.com/Nf6KnRzu [20:36:45] It's a lot easier to track your components, build and image, and deploy it locally or in the cloud with one file versus ? 60+ git clones? [20:36:45] I know you know how composer works, but I'm not sure you understand my workflow requirements.