Improving KDE Server Infrastructure
summary
KDE server configs move into Git and into automated ansible playbooks that install packages, deploy Apache files, enable SSL, restart services and recreate a site from scratch; local development uses a tool called background to spin Ubuntu VMs that run the same playbooks and bring up identity with MySQL PHP and LDAP. Documentation is rebuilt at sysadmind.kde.org. Result: fewer manual edits on production, testable changes locally, and straightforward pull requests for new contributors.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:26FINDING THE SERVER
- 2:09MAKING THE CHANGE
- 3:01WE COULD DO BETTER • Documentation is outdated
- 3:50NEW DOCUMENTATION
- 4:43MANAGING CONFIGURATION Åkademy We want it in version control
- 5:52ANSIBLE
- 7:22DEV VIRTUAL MACHINE
- 7:50VAGRANT
- 8:59RESULTS • Config is in version control We can experiment locally . You can help without server access
related talks
39mKDEs CI and CD Infrastructure
35mManaging a fleet of Linux desktops with Ansible
40mKDE Apps Initiative
43mAutomated server management with open source tools
36mMake your environment sane with Ansible Automation
39mAnsible - Your First Step Into Server Provisioning
44mPlatform Engineering in action
20mThe singularity is here for testing: genai advancements on kdevops