Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.
No edit summary
No edit summary
Line 26: Line 26:


# Fixed incorrect certificate call at "www.kenshidb.wiki" which was returning 403 and a bad handshake warning for the certificate we generated for Netdata during proxy server tests. Revoked certificate and...
# Fixed incorrect certificate call at "www.kenshidb.wiki" which was returning 403 and a bad handshake warning for the certificate we generated for Netdata during proxy server tests. Revoked certificate and...
# Created redirect for "[www.kenshidb.wiki www.kenshidb.wiki]" to appropriate present "https://kenshidb.wiki/w/Main_Page".
# Created redirect for "[www.kenshidb.wiki|www.kenshidb.wiki]" to appropriate 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.
# In so doing fixed the Google listing for "www.kenshidb.wiki" which now correctly paths to the frontpage of the website.
# Created a collection of scripts for managing the dashboards, recording metrics & storing the logs (securely).
# Created a collection of scripts for managing the dashboards, recording metrics & storing the logs (securely).

Revision as of 00:39, 22 March 2025

Maintenance Log

Return to the main page or
Return to the Maintenance Index
As of 3-18-25
  • Documentation (with pictures and examples) imported
  • Numerous server-side automations
  • Adoption of two dashboards for stronger internal monitoring:
  • Netdata (Works perfectly! Customizing... 3-18)
  • GoAccess (Also works perfectly! Even more customizing, Netdata is huge as is... 3-18)
  • 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.
  • These help me keep track of resource hogs, identify traffic anomalies and more effectively assess incident reports (if and when).
  • Synchronizing these with my BetterStack configuration (should) cover most ends in this regard. Surely there's more to be done...
  • Fiddling with various SEO-oriented aspects -> GoogleSearchConsole
  • Indexing! The site is now appropriately being crawled. (3-18)
  • Sitemap accepted, robots happy, on-site adjustments to follow. (3-18<)
  • Furtherance of server-sided security measures (we love the modern web)
  • Inquiries to and conversations with...
  • DigitalOcean - Particulars about metrics, extra firewall tweaks, load balancing, etc. Their docs are decent, their support actually answers.
  • MediaWikifolks - MediaWiki 1.44, Parsoid status, Extension updates, Extension depreciation, ideal package & library versions, etc.
  • Google - Rather, all site crawlers, the site's meta description, headers, so on and so forth. The Page Speeds tool is awesome!
3-21 notes
  1. Fixed incorrect certificate call at "www.kenshidb.wiki" which was returning 403 and a bad handshake warning for the certificate we generated for Netdata during proxy server tests. Revoked certificate and...
  2. Created redirect for "[www.kenshidb.wiki|www.kenshidb.wiki]" to appropriate present "https://kenshidb.wiki/w/Main_Page".
  3. In so doing fixed the Google listing for "www.kenshidb.wiki" which now correctly paths to the frontpage of the website.
  4. Created a collection of scripts for managing the dashboards, recording metrics & storing the logs (securely).
  5. Submitted a support ticket to DigitalOcean to inquire about a correct firewall configuration tunneling and cached-based connections will work along with regular traffic to the site.

Project:Updates not to be neglected -- I'll be organizing the Gadgets, Widgets, Modules & Extensions lists for that (ideally 3-23).