[00:02:22] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:30] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:46] PROBLEM - cp5 Puppet on cp5 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:48] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:50] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:54] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:56] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:04] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:22] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:42] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:50] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:58] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:04:02] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:04:16] PROBLEM - lizardfs1 Puppet on lizardfs1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:10:54] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [00:11:04] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [00:11:22] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [00:11:42] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [00:11:50] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [00:11:56] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [00:12:02] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [00:12:16] RECOVERY - lizardfs1 Puppet on lizardfs1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:20] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:28] RECOVERY - lizardfs2 Puppet on lizardfs2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:30] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:46] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:50] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:52] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:13:02] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:17:09] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [00:19:29] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpAvX [00:19:31] [02miraheze/mw-config] 07paladox 03c0e803f - Remove duplicate namespaces definition [02:05:09] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 6605 [02:05:10] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpATM [02:05:12] [02miraheze/services] 07MirahezeSSLBot 03179c661 - BOT: Updating services config for wikis [04:29:08] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [04:39:10] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 6627 [07:07:07] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [07:43:09] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 6631 [08:01:50] [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/fpAGg [08:01:52] [02miraheze/MirahezeMagic] 07translatewiki 035c21bb7 - Localisation updates from https://translatewiki.net. [08:01:53] [02miraheze/WikiDiscover] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpAGa [08:01:55] [02miraheze/WikiDiscover] 07translatewiki 035ec25c1 - Localisation updates from https://translatewiki.net. [08:01:56] [02miraheze/CreateWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpAGV [08:01:58] [02miraheze/CreateWiki] 07translatewiki 032d2a4a7 - Localisation updates from https://translatewiki.net. [08:01:59] [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpAGw [08:02:01] [02miraheze/ManageWiki] 07translatewiki 03f6d1cbe - Localisation updates from https://translatewiki.net. [08:44:01] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [08:52:01] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [10:11:08] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [11:19:46] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 3334 [11:24:44] Hello Nadelik! If you have any questions feel free to ask and someone should answer soon. [11:39:25] paladox: https://github.com/kulttuuri/DiscordNotifications/issues/19#issuecomment-447799469 yayy [11:39:28] Title: [ Allow multiple channels · Issue #19 · kulttuuri/DiscordNotifications · GitHub ] - github.com [11:40:12] paladox: do you remember which channels wanted it? [11:40:28] we should update the extension and roll out the change [11:41:19] Reception123: it’s in PrivateSettings.php currently [11:44:02] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [11:46:28] MacFan4000: ah, we need to change it to wgDiscordAdditionalIncomingWebhookUrls [11:52:02] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [12:12:32] Reception123: I forgot which wiki wanted that [12:31:08] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [13:30:52] PROBLEM - misc2 Redis Process on misc2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:30:56] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:31:08] PROBLEM - puppet1 Current Load on puppet1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:31:18] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:31:32] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:31:46] PROBLEM - misc2 Current Load on misc2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:32:00] PROBLEM - misc3 Disk Space on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:32:16] PROBLEM - puppet1 Disk Space on puppet1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:32:20] PROBLEM - misc2 Disk Space on misc2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:32:22] PROBLEM - misc2 HTTPS on misc2 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:34:12] PROBLEM - misc3 Current Load on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:34:14] PROBLEM - bacula1 Bacula Private Git on bacula1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [13:35:00] RECOVERY - misc2 Redis Process on misc2 is OK: PROCS OK: 1 process with args 'redis-server' [13:37:02] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:38:16] PROBLEM - lizardfs1 Puppet on lizardfs1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:38:28] PROBLEM - lizardfs2 Puppet on lizardfs2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:38:46] PROBLEM - cp5 Puppet on cp5 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:38:50] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:39:04] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:39:22] PROBLEM - misc2 Redis Process on misc2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:41:37] RECOVERY - puppet1 Current Load on puppet1 is OK: OK - load average: 3.05, 1.29, 1.01 [13:42:07] PROBLEM - misc3 SSH on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:45:46] Hello dish! If you have any questions feel free to ask and someone should answer soon. [13:46:23] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 5 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 2a00:d880:5:8ea::ebc7/cpweb, 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb [13:46:27] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb, 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb [13:47:19] PROBLEM - cp5 Varnish Backends on cp5 is CRITICAL: 1 backends are down. mw3 [13:47:23] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 2 backends are down. mw1 mw3 [13:48:25] RECOVERY - misc3 SSH on misc3 is OK: SSH OK - OpenSSH_7.4p1 Debian-10+deb9u4 (protocol 2.0) [13:49:19] RECOVERY - misc3 Current Load on misc3 is OK: OK - load average: 0.02, 0.10, 0.10 [13:50:05] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw2 [13:50:57] RECOVERY - puppet1 Disk Space on puppet1 is OK: DISK OK - free space: / 58564 MB (95% inode=99%); [13:51:19] RECOVERY - misc3 Disk Space on misc3 is OK: DISK OK - free space: / 58573 MB (95% inode=99%); [13:52:07] RECOVERY - misc2 Redis Process on misc2 is OK: PROCS OK: 1 process with args 'redis-server' [13:53:47] PROBLEM - misc3 Current Load on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:53:51] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:53:57] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:54:21] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:54:45] PROBLEM - misc3 SSH on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:55:13] PROBLEM - puppet1 SSH on puppet1 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:55:21] PROBLEM - puppet1 Current Load on puppet1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:55:47] PROBLEM - misc3 Disk Space on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:56:15] PROBLEM - misc2 Prometheus on misc2 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:56:23] PROBLEM - misc3 Restbase on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:56:29] PROBLEM - misc2 Redis Process on misc2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:56:33] PROBLEM - misc3 Electron on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:57:13] PROBLEM - misc3 Parsoid on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:57:23] PROBLEM - puppet1 Disk Space on puppet1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [13:57:51] PROBLEM - misc2 SSH on misc2 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:58:32] PROBLEM - Host misc3 is DOWN: PING CRITICAL - Packet loss = 100% [13:58:46] PROBLEM - Host puppet1 is DOWN: PING CRITICAL - Packet loss = 100% [13:59:10] PROBLEM - Host misc2 is DOWN: PING CRITICAL - Packet loss = 100% [13:59:30] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [13:59:50] RECOVERY - bacula1 Bacula Private Git on bacula1 is OK: OK: Full, 2129 files, 3.465MB, 2018-12-16 03:29:00 (1.4 days ago) [14:00:24] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [14:00:26] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [14:00:32] RECOVERY - Host misc3 is UP: PING OK - Packet loss = 0%, RTA = 1.22 ms [14:00:38] RECOVERY - misc3 Electron on misc3 is OK: TCP OK - 0.001 second response time on 185.52.1.144 port 3000 [14:00:46] RECOVERY - Host puppet1 is UP: PING OK - Packet loss = 0%, RTA = 0.40 ms [14:00:58] RECOVERY - misc3 SSH on misc3 is OK: SSH OK - OpenSSH_7.4p1 Debian-10+deb9u4 (protocol 2.0) [14:01:10] RECOVERY - Host misc2 is UP: PING OK - Packet loss = 0%, RTA = 0.60 ms [14:01:12] RECOVERY - misc3 Parsoid on misc3 is OK: TCP OK - 0.001 second response time on 185.52.1.144 port 8142 [14:01:16] RECOVERY - puppet1 SSH on puppet1 is OK: SSH OK - OpenSSH_7.4p1 Debian-10+deb9u4 (protocol 2.0) [14:01:22] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [14:01:24] RECOVERY - puppet1 Disk Space on puppet1 is OK: DISK OK - free space: / 58567 MB (95% inode=99%); [14:01:26] RECOVERY - puppet1 Current Load on puppet1 is OK: OK - load average: 2.40, 1.28, 0.50 [14:01:40] RECOVERY - misc2 SSH on misc2 is OK: SSH OK - OpenSSH_7.4p1 Debian-10+deb9u4 (protocol 2.0) [14:01:44] RECOVERY - misc2 Current Load on misc2 is OK: OK - load average: 0.39, 0.46, 0.19 [14:02:06] RECOVERY - misc3 Current Load on misc3 is OK: OK - load average: 2.62, 2.23, 0.92 [14:02:28] RECOVERY - misc3 Restbase on misc3 is OK: TCP OK - 0.001 second response time on 185.52.1.144 port 7231 [14:03:04] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [14:08:28] RECOVERY - lizardfs2 Puppet on lizardfs2 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:10:50] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:11:02] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [14:11:22] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:11:26] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [14:11:32] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:11:50] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [14:11:56] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [14:12:16] RECOVERY - lizardfs1 Puppet on lizardfs1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [14:12:20] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [14:12:37] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [14:12:46] RECOVERY - cp5 Puppet on cp5 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:12:52] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [14:25:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpASw [14:25:13] [02miraheze/services] 07MirahezeSSLBot 033d36a86 - BOT: Updating services config for wikis [15:43:56] RECOVERY - misc2 HTTPS on misc2 is OK: HTTP OK: HTTP/1.1 200 OK - 44907 bytes in 0.351 second response time [15:57:12] Hi! Just contacting you to tell that here are no high priority open tasks. Nice job! [16:41:14] time to raise normal ones to high [16:41:54] mutante ? :) [16:42:19] paladox: are you ignoring ZppixBot ?:) [16:42:26] nope [16:42:29] i doin't think so [16:42:39] well, i was responding to it [16:42:46] ah heh [17:28:42] !log sudo -u www-data php /srv/mediawiki/w/maint*/rebuildLocalisationCache.php --wiki loginwiki on mw* [17:28:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:57:10] !log sudo -u www-data php /srv/mediawiki/w/maintenance/importDump.php --wiki=visewiki --report=1 visetestwiki.xml on mw1 ref T3865 [17:57:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:21:29] Mutante: Thank you for caring about me! :) [18:23:28] ZppixBot: lol, you are welcome. i was just saying "if you run out of high prio stuff it just means the normal stuff now becomes high prio" [18:23:46] because as we learn from andre__, prio reflects reality not wishes *gg* [18:31:01] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_32 [+0/-0/±2] 13https://git.io/fpxqN [18:31:03] [02miraheze/mediawiki] 07paladox 032730c69 - Update Echo and liberty [18:32:02] mutante: hi. that was me by the way :P [18:32:35] that is a smart way to put things, maybe we should try that [18:34:16] Reception123: just quoting it from WMF phab :) [18:36:41] heh [18:36:54] I really wonder how Andre manages to sort all those tasks [18:37:23] so many coming in all the time, having to be triaged and many times he also helps on the actual issue [18:37:51] well, it's like his full time job [18:37:53] afaict [18:38:03] and he has many years of exp doing that thing [18:38:08] with Bugzilla for Mozilla and stuff [18:38:20] probably has a bunch of templates to reply faster [18:41:22] mutante: yeah, probably has a huge database and he drags answers from there [18:41:54] since just from personal experience I know I've got the same reply multiple times ;) [18:42:03] maybe database = text files, but yea [18:42:21] "canned responses" is the term [18:42:34] phab itself should support them [19:27:23] hello [19:28:25] I would like to add a redirect to my custom domain (www.example.com), so that if someone types example.com, they will get to my site. How can I do that? [19:34:16] I understand that this can be done with editing .htaccess file. I don't know if I have access to this file. Is there another way to do it? [20:27:41] unmannedkite: hi [20:28:04] unmannedkite: you don't need to do that if you have a custom domain with us, we can do it for you [20:28:18] please specify your domain/ make a Phab request [20:28:31] mutante: that would be great especially for us where we still can give standard responses to users [20:29:35] Reception123: yep, i think the simplest way is to store template text in Phab pastebins and copy/paste. and then there are custom forms as well [20:29:57] yeah, that would be great [20:30:19] mutante: too bad Phab doesn't really accept feature suggestions anymore (at least that's what I saw a while ago when I had something in mind) [20:30:42] Reception123: yea, i think "only for money" [20:30:51] aka as "sponsored feature" or so [20:34:14] yeah [20:34:30] well I guess they do need the money [20:34:42] paladox: Thank you very much for the import -- I did not ever think I would have a good way to access that data again! [20:34:52] dayid your welcome :) [20:34:53] it's hard for non-profits/open-source projects to advance without enough (I know how it is :P) [20:35:10] dayid: If you need anything else please feel free to contact us and we'd be happy to help :) [20:35:12] It wasen't hard to restore either, just needed to rename tables (that had the mw_) prefix. [20:36:53] :) [20:36:59] paladox: My trouble was (back in 2017) I got caught by my OS updating the mediawiki - it kept telling me my old tables were bad and eventually I gave up :( [20:37:06] err - mysql and mediawiki [20:37:09] alas - I appreciate it. [20:37:10] oh [20:37:24] Yeah, if the versions are old that happens [20:37:42] well, we're always happy to help [20:37:44] Reception123, you can do that even if I my custom domain is defined with the CNAME entry (I only referred the CNAME (*) of my domain to mw-lb.miraheze.org and didn't change the name servers to "ns1.miraheze.org" and "ns2.miraheze.org")? [20:38:18] you need to set your other domain to poin't to mw-lb.miraheze.org too. [20:38:58] paladox, you're answer is to my question? [20:39:05] yep [20:39:44] So ie if you have a domain pointing at us, lets say wiki.x.com and you want x.com to redirect to wiki.x.com, you need to poin't x.com at mw-lb.miraheze.org so that we can add some redirects. [20:39:59] what is my "other domain"? I set under CNAME that * (all) will refer to mw-lb.miraheze.org [20:40:10] unmannedkite: oh, if it is * we can do that yeah [20:40:19] we just need to generate another cert for the wiki and then redirect it locally [20:40:26] ^ paladox [20:40:32] yep [20:40:40] could you please take care of it? (a bit busy atm if not I can do it later) [20:40:44] yup [20:40:50] paladox: you just need to generate a www. cert and then add it to redirects [20:40:59] unmannedkite which domain do you want redirected? [20:41:16] Reception123 i think they want x.com to redirect to www.x.com [20:41:49] paladox: oh, then you just inverse it (you generate www, you change that in certs+MW and then you add the other current domain to redirects) [20:42:20] unmannedkite also which domain do you want it redirected too? [23:32:51] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpxrJ [23:32:52] [02miraheze/mw-config] 07paladox 03cb8f946 - hypernostalgia -> hypernostalgiawiki