BoroondaraWiki:Community portal: Difference between revisions

From Boroondara Wiki
(→‎HTTPS: new section)
(→‎Upgrade to 1.30.0: Mobile frontend)
Tags: Mobile edit Mobile web edit
(5 intermediate revisions by the same user not shown)
Line 20: Line 20:


:Well that clearly didn't work... I'll be working on a number of other strategies for the long-term. In the meantime, I have temporarily disabled registrations until I can implement these measures and make sure that they are configured properly. [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 01:06, 1 August 2016 (UTC)
:Well that clearly didn't work... I'll be working on a number of other strategies for the long-term. In the meantime, I have temporarily disabled registrations until I can implement these measures and make sure that they are configured properly. [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 01:06, 1 August 2016 (UTC)
::I have just re-enabled user registration after introducing a raft of new measures, including forced HTTPS, enhanced CAPTCHS at user registration and new anti-spam blacklists. I guess we'll see how this goes... [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 15:53, 27 April 2017 (AEST)


== Upgrade to 1.27 ==
== Upgrade to 1.27 ==
Line 37: Line 39:


If you encounter any issues, [[User_talk:Philip|please let me know]]. [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 22:04, 6 February 2017 (AEDT)
If you encounter any issues, [[User_talk:Philip|please let me know]]. [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 22:04, 6 February 2017 (AEDT)
== Server migration ==
After months of below-par load times, BoroondaraWiki is moving to a new server. This will necessitate disabling editing for at least 12 hours to avoid file conflicts, DNS conflicts and losing edits. I will post again here when the migration is completed. Apologies for any inconvenience. [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 10:31, 26 September 2017 (AEST)
:Thank you for your patience - the migration has been completed! There doesn't seem to be anything wrong, but in case you find something, please let me know on my talk page. [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 15:35, 27 September 2017 (AEST)
::I might just add that this has improved our server load time by almost five seconds from 11.7s on the old server to 7.0s on this new one. Hopefully this is a noticeable improvement! [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 15:38, 27 September 2017 (AEST)
== Upgrade to 1.30.0 ==
To keep up with changes in extension compatibility, I have upgraded the wiki to the latest version (1.30.0) today. Please let me know if anything is not working. [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 21:43, 17 February 2018 (AEDT)
:Apologies for the issues with the mobile frontend. It seems that the extension makers initiated a wiki-breaking change and hid it into the release notes. Should all be fixed now. [[User:Philip|Philip]] ([[User talk:Philip|talk]]) 19:43, 27 March 2018 (AEDT)

Revision as of 19:43, 27 March 2018


New domain!

An update as of today - BoroondaraWiki has evolved from its temporary .xyz domain name to the permanent .org domain. The old boroondarawiki.xyz will still continue to redirect to the current site for the foreseeable future. If this has broken anything or caused any issues, please let me know. Philip (talk) 13:41, 10 July 2016 (UTC)

Influx of spam

If anybody has been keeping an eye on Special:RecentChanges recently, you will have seen the wave of spambot registrations recently. I've just added a DNS blocklist so hopefully this will help to cut down on their numbers. We'll see how it goes... Philip (talk) 13:09, 27 July 2016 (UTC)

Well that clearly didn't work... I'll be working on a number of other strategies for the long-term. In the meantime, I have temporarily disabled registrations until I can implement these measures and make sure that they are configured properly. Philip (talk) 01:06, 1 August 2016 (UTC)
I have just re-enabled user registration after introducing a raft of new measures, including forced HTTPS, enhanced CAPTCHS at user registration and new anti-spam blacklists. I guess we'll see how this goes... Philip (talk) 15:53, 27 April 2017 (AEST)

Upgrade to 1.27

As of today, the wiki is running on the latest MediaWiki software, version 1.27.1 (https://www.mediawiki.org/wiki/MediaWiki_1.27). I postponed upgrading until the first minor release came out to help address any security/other issues before they arise. Everything should be working fine, but in case it isn't, please let me know. Philip (talk) 05:16, 22 September 2016 (UTC)

Trello board

If anybody is interested in seeing the ongoing maintenance and development tasks for the wiki's backend, check out the Trello board (now public!) https://trello.com/b/PLFLOs5T/boroondarawiki-development Philip (talk) 09:25, 28 December 2016 (UTC)

HTTPS

For everyone's information, SSL has now been enabled by default across BoroondaraWiki. All pages should now read:

https://boroondarawiki.org/wiki/PAGENAME.

If you encounter any issues, please let me know. Philip (talk) 22:04, 6 February 2017 (AEDT)

Server migration

After months of below-par load times, BoroondaraWiki is moving to a new server. This will necessitate disabling editing for at least 12 hours to avoid file conflicts, DNS conflicts and losing edits. I will post again here when the migration is completed. Apologies for any inconvenience. Philip (talk) 10:31, 26 September 2017 (AEST)

Thank you for your patience - the migration has been completed! There doesn't seem to be anything wrong, but in case you find something, please let me know on my talk page. Philip (talk) 15:35, 27 September 2017 (AEST)
I might just add that this has improved our server load time by almost five seconds from 11.7s on the old server to 7.0s on this new one. Hopefully this is a noticeable improvement! Philip (talk) 15:38, 27 September 2017 (AEST)

Upgrade to 1.30.0

To keep up with changes in extension compatibility, I have upgraded the wiki to the latest version (1.30.0) today. Please let me know if anything is not working. Philip (talk) 21:43, 17 February 2018 (AEDT)

Apologies for the issues with the mobile frontend. It seems that the extension makers initiated a wiki-breaking change and hid it into the release notes. Should all be fixed now. Philip (talk) 19:43, 27 March 2018 (AEDT)