[00:41:44] hey whats the best free host? [00:42:26] Could name a few. What's the purpose of your wiki? [00:42:52] NATO CYBERCOM working group - we're going to be holding a global public workship in the comming weeks [00:43:08] schedule being negoiated with SHAPE as we speak [00:43:52] Can the wiki be public? Are you ok with sharing user accounts with other wikis on that wiki host? Any national security concerns? [00:44:22] yes it will be public, write access restricted - a bridge into WIF would be awesome [00:45:18] If it can be public but write access restricted and there's no national security concerns, there's probably only 2 choices. Miraheze and ShoutWiki. [00:45:49] what are the differences? [00:46:46] Miraheze is probably going to be a bit better. They are using the latest version of MediaWiki and have an active community. I think ShoutWiki has per-wiki user account systems, but on Miraheze, the users system is shared between all the wikis [00:47:00] btw I congratualate you for using your given name as your nick [00:47:24] Lol, it's because I have to use this for my job :) [00:47:40] You might know me as Odyss3us and Crusher [00:48:05] If you don't mind paying a tad bit of money, there's more options that will probably allow you to have all your wishes. https://www.mediawiki.org/wiki/Hosting_services [00:48:05] of course now I play with a valid email address :) [00:48:36] yeah I would love to but until we get funded I can't do that [00:48:43] Some of them are hosts that offer 1-click setup of MediaWiki but it requires you to have some technical background and it doesn't come with all the fancy extensions [00:49:08] I wish I still had an active Azure acct [00:49:14] there's a couple great packages on there [00:49:27] Ah too bad I can't share my $150/mo credit with you [00:49:39] on Azure? [00:49:50] I hadn't thought about deploying MW on Azure, that might work, if you can figure out their MySQL offering [00:49:57] I might be able to make that worth your while actually [00:49:58] Yes, on Azure. I worked for Microsoft [00:50:10] want to see something wild? [00:50:32] I'm afraid I cannot share this subscription for personal gain [00:51:00] https://pastebin.com/Nbd6Xq3N [00:53:06] look at the time stamps.... he replied in 7min! [00:55:38] I need to use Azure's dns management for this: http://wiki.development.exchange (look at the domain, 7 page paper on what we're trying to do) [00:56:20] actually to really do it right I need to write a custom nameserver [00:57:24] I believe the few other wiki hosts that have plans for less than $20/mo are MyWikis and Wiki-Valley [00:57:53] yeah if I do that I might as well just go the Azure route and find someone to sponsor it [00:58:07] Then you've got Professional.Wiki, Wikibase Solutions, WikiTeq, WikiWorks, etc. if you really need to build up your wiki and need professional consulting [00:59:04] You can get a cheap VPS with minimal RAM and do so if you'd like. gdnsd doesn't need more than 100MB of RAM [00:59:48] Azure abstracts all of that from me which I love [01:00:05] and now that linux vms are finally stable it should be very smooth [01:00:19] I don't think I would enjoy using Azure to deploy MediaWiki [01:00:27] it was actually only several clicks to deploy wikimedia in 2018 [01:01:13] obviously we'd need to use PS to automate it, but from my understanding those libs have really matured [01:01:46] are you on linkedin? [01:01:47] https://www.linkedin.com/company/space-force/ [01:01:57] In my opinion, Azure is still difficult to use and there's probably a lot of moving parts that would make maintenance difficult. Cloud providers do make running MediaWiki more complicated. For instance, we tried to use AWS Elasticsearch for CirrusSearch, but it didn't work. Ended up just using our own server and it works like a charm. [01:02:05] I own that "company" [01:02:47] see http://multiplex.studio/files/CognitiveCyberwar.pdf page 13 [01:09:03] JeffreyWang[m]: want to jump on teams later when you're off mobile [01:09:47] Did you need more help with selecting a wiki host? [01:09:59] the M what ever is what I'm going with [01:10:21] I want to talk bigger picture, I get the feeling we have alot to talk about [01:11:21] I have an 12 user E3 O365 tenant [01:11:44] actually its been open since MSOS days [01:12:07] w/ audio callin [01:12:19] Cool, good luck. If you are interested in paid consulting, I am available. Not sure what the rules are here for self advertising so I won't get into it, but you can find consultants on mediawiki.org if you are interested. [01:14:09] well thank you for your time, look forward to trying this service out (sweet David Bowie's Space Oddity is playing on http://radioparadise.com) [01:14:37] My name isn't under there, but the companies I work for are [01:15:20] http://multiplex.studio/files/jlind_resume_std.pdf [01:16:22] my biggest success was authoring and managing the production of Northern Trust's .NET 3.5 enterprise library in 2009-2010. Still used by 800+ apps and 3000ish devs [01:17:52] you know my email, just a warning Yahoo!'s spam detection is a little wonky and has false positives that don't get fwd'd to O365 [01:18:25] I try to check the spam folder daily but sometimes I don't get around to it [01:19:36] hmmm that resume link is bad [01:20:02] http://wwidew.net/jlind_resume_std.pdf i think [01:21:55] yup [01:22:14] you a star trek fan JeffreyWang[m] ? [09:02:39] MediaWiki core shouldn't send deprecation warnings, right? I mean, if no extension is installed or responsible for those warnings [09:04:23] I ask because it's sending deprecation warnings about Revision, which clogs the 'error' log channel. I'd like to avoid disabling that channel on production [09:10:14] Oh, looks like I solved the issue adding & ~E_USER_DEPRECATED to the error_reporting php setting [09:54:20] Vulpix your fix is just ignoring the issue, but it should be addressed - the Revision class has been removed, so what deprecation warnings are you seeing? [10:00:50] DannyS712: there are some Revision() constructor calls in mediawiki-1.36.1/includes/Storage/PageUpdater.php [10:18:32] those were guarded behind other hard deprecated code and thus the Revision objects were only created if there was something else that was deprecated and being used, which shouldn't have been the case with just core [10:56:26] That's true for some of them like hooks, but there are others that are called directly from private methods [23:14:37] Hi guys, I updated mw 1.31 to 1.35 and now I get "Unknown column 'rev_user_text' in 'field list'". Is there a script that I can run to fix that? [23:15:03] update your extensions