1 / 14

Maintaining a Learning Management System in 10 Easy Steps

Maintaining a Learning Management System in 10 Easy Steps. David Millians millia@uga.edu · @millia13 @ ugaetc University of Georgia Educational Technology Center. LMS (& CMS). What is… Linux vs. Windows Remote vs. Local Hosting Source Programming Language. 1. Install & Log.

sai
Download Presentation

Maintaining a Learning Management System in 10 Easy Steps

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Maintaining a Learning Management System in 10 Easy Steps David Millians millia@uga.edu· @millia13 @ugaetcUniversity of GeorgiaEducational Technology Center

  2. LMS (& CMS) • What is… • Linux vs. Windows • Remote vs. Local Hosting • Source Programming Language

  3. 1. Install & Log • Write down what you do! • Paste URLs • Note all the fiddly bits • Write down passwords (!) • Planning • Storage • Performance

  4. 2. Updates • Yes, really. • Main OS • Main Servers • “Fiddly Bits” • LMS • Automatic vs. Manual • Mailing Lists

  5. 3. Script ScriptScript • Windows • PowerShell, VBS… or Perl, Shell, et al • Linux • Perl, BASH, et al • Why? • Reliability • Reproducibility • Scheduling

  6. 4. Delegate • Monkey Theory • LMS has many features • You Can’t Know Them All • You Have to Know the Other Stuff • You Can Figure it Out

  7. 5. Tools – Use Them • Macho Men Use The Command Line • Meanwhile, for the rest of us: • PhpMyAdmin • Nagios • Firewall frontends/builders • Google; Stack Overflow; Server Fault; SuperUser • Somebody else was Lazy

  8. 6. Permissions • Ugh. • New “Users” for Servers • New User Accounts in Servers • IP Blocking • Real User permissions

  9. 7. Network Security • Firewall • Internal Routing • Hard Coding

  10. 8. Backup • VM • Packages • Raw • Source/Configs • DB (Not Files) • Data

  11. 9. Test Backups • Restore VM • Move to other platform

  12. 10. Monitor & Tune • Nagios • Atop • Windows Admin Tools

More Related