AFSWiki Administration
From AFSWiki
Contents |
Purpose
The goal of this page is to agree upon standard practices and procedures for common AFS Wiki Admin tasks. Please consult this list (and add to it) whenever you are about to make changes to our software, database, configurations, etc.. Please also feel free to use the Talk: feature to discuss any policy points.
User New-Account and Password Related
- AFSWiki Request New User Process
- AFSWiki Add New User Process
- Standards for Creation and Content of User Pages
- AFSWiki New User Confirmation Email Template (deprecated)
- AFSWiki Change Username Process
- AFSWiki Forgot Password Process
- AFSWiki Import Users Process
User Rights and User Configuration
- Private:AFSWiki Edit Anonymously Readable Whitelist - (no longer used)
- AFSWiki sysadmin mailing list
- AFSWiki Change Any User's Password
- AFSWiki Deactivate User Account - (specifically does not delete the account)
General
- AFS Admin Todo
- AFSWiki SysAdmin Mailing List Administration
- Backups. A subdirectory of ~/ called backups contains files named YYYYMMDD-backup.sql. You can read how to create a backup whenever you would like in ~/backups-HOWTO. At this time, we retain all backups. When we run into space considerations, we can revise this policy.
Do's and Don't's
Do's - when working with system files:
- before doing work, check AFSWiki Administration to see if there's a standard procedure for the task. If so, follow the SOP. If not, and you're doing something that will be done again, consider writing a new SOP.
- log your changes by appending notes about the changes you make to ~/sysadmin.txt
- get a second opinion and code review from another sysadmin before installing new software, making changes, etc.. It is best to review these changes with the whole mailing list. However, if you can't for some reason, you must at least have one other person review your changes.
- use the test environment to test changes (forthcoming)
- make a copy of the LocalSettings.php file before you change it. Copy it to ~/backups/ as "LocalSettings.php.date-your initials". For multiple versions (should you need them, which would be uncommon), you can call them "LocalSettings.php.date-vx-your initials". An example would be: LocalSettings.php.20071004-v2-NG. After the backup, log your changes to the changelog.txt.
Don't
- Don't delete an account-- deactivate it. Deleting accounts can orphan content created by those accounts.
