More actions
No edit summary |
No edit summary |
||
(35 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
;[[Main Page|Return to the main page]] or | ;[[Main Page|Return to the main page]] or | ||
;[[Project:Maintenance|Return to the Maintenance Index]] | ;[[Project:Maintenance|Return to the Maintenance Index]] | ||
; | ;Date 3-23-25 | ||
;Period 8PMEST-10PMEST | |||
;Changes | |||
---- | |||
===Revised [[Project:Extensions|Extensions]] list=== | |||
---- | |||
====Dashboards and Monitoring==== | |||
*Adoption of two dashboards for stronger internal monitoring: | *Adoption of two dashboards for stronger internal monitoring: | ||
:*[https://www.netdata.cloud/ Netdata] | :*[https://www.netdata.cloud/ Netdata] | ||
:*[https://goaccess.io/ GoAccess] ( | :*[https://goaccess.io/ GoAccess] | ||
::*These modern monitoring tools are crazy good. Easy to access and use. However... | :*Additional tools in use - | ||
::*Due to the way they expose sensitive server information they won't be publicly accessible. | ::*atop/htop (We love the terminal!) | ||
::* | ::*Fail2Ban | ||
:: | ::*Logwatch | ||
* | ::*Multitail | ||
* | :::*...Others like Logtail require some more tweaking for proper integration. | ||
:::*These modern monitoring tools are crazy good. Easy to access and use. However... | |||
:::*Due to the way they expose sensitive server information they won't be publicly accessible. | |||
:::*Helps me keep track of resource hogs, identify traffic anomalies and more effectively assess incident reports (if and when). | |||
:; 3-22 notes | |||
:# Pivoted away from [https://dashy.to/ Dashy] before even starting (an absurd amount of vulnerabilities wrapped in one npm install package!) | |||
:# Orienting towards a simpler, custom-fit dashboard to combine all metrics (including curated Netdata and GoAccess outputs), logs ''and'' recent changes. | |||
:# Automated the aforementioned to my needs. All internal services have consistent albeit basic access and archival methods in place. | |||
:# Created a collection of scripts for managing the dashboards, recording metrics & storing the logs (securely). | |||
:;Three external monitors | |||
::DigitalOcean (''Host'') - Various opt-in metrics, notifications and a responsive support team. | |||
::[https://betterstack.com/ BetterStack] More granular at free tier than UptimeRobot. | |||
::[https://uptimerobot.com/ UptimeRobot] Most basic monitor for sanity checking. Minimal offerings at free tier. | |||
:; For me, this covers the level of redundancy and monitoring I'm looking for. It covers both internal and external services, allows parity checking, comparison and historic logs I can review over time. | |||
---- | |||
====SEO Updates==== | |||
:*Indexing! The site is now appropriately being crawled. (3-18) | |||
:*Sitemap accepted, robots happy, on-site adjustments to follow. (3-18<) | |||
:* Fixed incorrect certificate call at "www.kenshidb.wiki" which was returning 403 and a bad handshake warning. Revoked previously generated certificate for Netdata during proxy server testing, allowing for... | |||
:* Creation of redirect for "[https://www.kenshidb.wiki www.kenshidb.wiki]" to appropriately present "https://kenshidb.wiki/w/Main_Page". | |||
:* In so doing fixed the Google listing for "[https://www.kenshidb.wiki www.kenshidb.wiki]" which now correctly paths to the frontpage of the website and does not crawl as a 403. | |||
---- | |||
*Inquiries to and conversations with... | *Inquiries to and conversations with... | ||
:*DigitalOcean - Particulars about metrics, extra firewall tweaks, load balancing, etc. Their docs are decent, their support actually answers. | |||
::*Talks ongoing from 3-21 to 3-23. Essentially finished. | |||
:*MediaWikifolks - MediaWiki 1.44, SemanticMediaWiki 5.0.0, Parsoid status, Chart (alternatives), other Extension updates, Extension depreciation, ideal package & library versions, etc. PHP 8.1 is becoming the baseline, that goalpost still may move forward soon enough. | |||
---- | |||
====Mobile Note==== | |||
;As a personal aside I spent a few hours browsing the website on my phone throughout the week and especially on 3-23. From my limited testing the skin was functioning pretty well! I'd love some feedback for anyone trying out the site on a mobile device - the site should be mobile-friendly! | |||
---- | ---- | ||
[[Project:Updates]] not to be neglected -- I'll be organizing the Gadgets, Widgets, Modules & Extensions lists for that (ideally 3-23). | [[Project:Updates]] not to be neglected -- I'll be organizing the Gadgets, Widgets, Modules & Extensions lists for that (ideally 3-23). | ||
---- | |||
;Upcoming Maintenance | |||
;Date 3-30-25 | |||
;See [[Project:Maintenance/033025]] |
Latest revision as of 02:00, 24 March 2025
Maintenance Log
- Return to the main page or
- Return to the Maintenance Index
- Date 3-23-25
- Period 8PMEST-10PMEST
- Changes
Revised Extensions list
Dashboards and Monitoring
- Adoption of two dashboards for stronger internal monitoring:
-
- atop/htop (We love the terminal!)
- Fail2Ban
- Logwatch
- Multitail
- ...Others like Logtail require some more tweaking for proper integration.
- These modern monitoring tools are crazy good. Easy to access and use. However...
- Due to the way they expose sensitive server information they won't be publicly accessible.
- Helps me keep track of resource hogs, identify traffic anomalies and more effectively assess incident reports (if and when).
- 3-22 notes
- Pivoted away from Dashy before even starting (an absurd amount of vulnerabilities wrapped in one npm install package!)
- Orienting towards a simpler, custom-fit dashboard to combine all metrics (including curated Netdata and GoAccess outputs), logs and recent changes.
- Automated the aforementioned to my needs. All internal services have consistent albeit basic access and archival methods in place.
- Created a collection of scripts for managing the dashboards, recording metrics & storing the logs (securely).
- Three external monitors
- DigitalOcean (Host) - Various opt-in metrics, notifications and a responsive support team.
- BetterStack More granular at free tier than UptimeRobot.
- UptimeRobot Most basic monitor for sanity checking. Minimal offerings at free tier.
- For me, this covers the level of redundancy and monitoring I'm looking for. It covers both internal and external services, allows parity checking, comparison and historic logs I can review over time.
SEO Updates
- Indexing! The site is now appropriately being crawled. (3-18)
- Sitemap accepted, robots happy, on-site adjustments to follow. (3-18<)
- Fixed incorrect certificate call at "www.kenshidb.wiki" which was returning 403 and a bad handshake warning. Revoked previously generated certificate for Netdata during proxy server testing, allowing for...
- Creation of redirect for "www.kenshidb.wiki" to appropriately present "https://kenshidb.wiki/w/Main_Page".
- In so doing fixed the Google listing for "www.kenshidb.wiki" which now correctly paths to the frontpage of the website and does not crawl as a 403.
- Inquiries to and conversations with...
- DigitalOcean - Particulars about metrics, extra firewall tweaks, load balancing, etc. Their docs are decent, their support actually answers.
- Talks ongoing from 3-21 to 3-23. Essentially finished.
- MediaWikifolks - MediaWiki 1.44, SemanticMediaWiki 5.0.0, Parsoid status, Chart (alternatives), other Extension updates, Extension depreciation, ideal package & library versions, etc. PHP 8.1 is becoming the baseline, that goalpost still may move forward soon enough.
Mobile Note
- As a personal aside I spent a few hours browsing the website on my phone throughout the week and especially on 3-23. From my limited testing the skin was functioning pretty well! I'd love some feedback for anyone trying out the site on a mobile device - the site should be mobile-friendly!
Project:Updates not to be neglected -- I'll be organizing the Gadgets, Widgets, Modules & Extensions lists for that (ideally 3-23).
- Upcoming Maintenance
- Date 3-30-25
- See Project:Maintenance/033025