History: Infrastructure Team
Preview of version: 125
The Infrastructure Team is responsible for *.tiki.org hosting, server administration, domains, uptime, etc. AKA: devops, sysadmin.
Table of contents
- Release responsibilities
- Ongoing responsibilities
- Fix and close
- 1.1.1. transition from tikiwiki.org to tiki.org
- 1.1.2. Activate the removal of www for all sites
- 1.1.3. Clean up permissions on tiki.org
- 1.1.4. Images lost on dev.tw.o
- 1.1.5. Rewrite Rules
- 1.1.6. dev.tiki.org -> delete from user list all users that are not necessary here
- 1.1.7. Delete a pic
- 1.1.8. Move calendar data from dev to info site
- Major projects
- 1.1.1. Move phpxref to own subdomain
- 1.1.2. Doxygen
- 1.1.3. phpDocumentor
- 1.1.4. Dogfood TRIM
- 1.1.5. Round Robin / Redundancy / Disaster planning for all *.tiki.org content
- 1.1.6. Setup a monitoring solution
- 1.1.7. Implement Single Sign On (SSO) on 6 main sites.
- 1.1.8. Code stats
- 1.1.9. Community Mail Server
- Related links
Release responsibilities
- Progressively update each Domain to the new version, and the Dogfood Team's plan.
- The goal is that all major sites are upgraded before it's released.
Ongoing responsibilities
This page is to coordinate work and list requests about various aspects of *.tiki.org sites and community tools
This has previously been done by email. We will do it wiki way so at any given time, we'll know what needs to be done.
This is not a list of feature requests, which should be done at: http://dev.tiki.org. If it's Tiki bug, it's ok to put below but with a link to dev.tiki.org as well but know that while the infrastructure team can help detect/confirm a bug, it is not expected to correct bugs, but to update the sites as soon as they are corrected.
Do not put any security or sensitive info below. Instead, contact http://security.tiki.org
1.1.1. Hosting the *.tiki.org sites
1.1.2. Maintain list of hacks adaptations to Tiki sites, or use SVN or TRIM.
In the past, it's happened that we had specialized changes to Tiki (ex.: message templates, custom plugins, etc.). And then, sometimes, these get wiped with a clean install of Tiki. While we should try to stay as close as possible to Tiki code dogfood, when we do not, it should be documented or we use TRIM/SVN and have it make a report of all diffs (or something)
Rewrite Rule collisions
http://tiki.org/stats gives me error but http://tiki.org/Stats is ok.
htaccess
Please create the wiki pages if the access has been or should be modified
- htaccess doc
- htaccess dev (will need calendar redirect)
- htaccess community
- htaccess profiles
- htaccess info
- htaccess themes
1.1.3. Keep all sites up to date & making Intertiki work
- All our sites should be recent versions of the branch
- The revision number should be visible so everyone knows to indicate if the see a bug
1.1.4. Backups
- Each host should make send backups to another. Can be done by TRIM
1.1.5. Manage DNS, domain name and email accounts
- Managing the DNS info for the various Domains (changi)
- Domain names MarcLaporte
- Community Mail Server @tiki.org emails (Marc but looking for replacement)
- SSL (changi)
- Community Server renewal, payments, etc. (Changi)
1.1.6. Maintain Pre-Dogfood server
Fix and close
1.1.1. transition from tikiwiki.org to tiki.org
- Setup permanent redirect from tikiwiki.org to tiki.org
- Setup the cdn for each
- will redirect of http://tikiwiki.org/stable.version cause an issue? (like InterTiki)
1.1.2. Activate the removal of www for all sites
New option in Admin -> General -> Navigation "Domain prefix handling" which would be nicer than the "Are you lost ?" at http://www.doc.tiki.org/
1.1.3. Clean up permissions on tiki.org
Tiki.org has a lot of legacy perms. Ex.: workspace (aulawiki), homework, jukebox, etc. They should be removed from http://tiki.org/tiki-objectpermissions.php along with any assignments. Todo: Take a Tiki 5.x clean install, and compare.
1.1.4. Images lost on dev.tw.o
See here: http://dev.tiki.org/TrackerFieldUIRevamp
Image missing:
http://dev.tiki.org/img/wiki_up/trackerui1.png
and two images here: http://dev.tiki.org/Translation+Editor+Revamp (tiki-download_wiki_attachment.php?attId=88) perhaps issue between 5.0 and 5.1 ?
More here:
http://dev.tiki.org/Code+Howto:+Copy+reproduce+a+change+from+one+branch+to+another
Still available for old server. (ask Marc for access)
1.1.5. Rewrite Rules
I posted a comment here with a link to http://doc.tiki.org/categories and I get http://doc.tiki.org/tiki-browse_categories.php instead of http://doc.tiki.org/tiki-index.php?page=categories
same problem with http://doc.tiki.org/calendar
dev is ok:
http://dev.tiki.org/categories
1.1.6. dev.tiki.org -> delete from user list all users that are not necessary here
1.1.7. Delete a pic
http://tiki.org/img/wiki_up//spiderdog_in_action.png
1.1.8. Move calendar data from dev to info site
Check with Rick 1st
With a persistent rewrite rule . Now: Upcoming Events
Major projects
1.1.1. Move phpxref to own subdomain
From de.tiki.org/xref-trunk/ to phpxref.tiki.org and make sure to add a redirect 301 for search engines
1.1.2. Doxygen
We used to have http://de.tiki.org/dox-trunk/html/, but it's gone now. Do we re-install? If so, at doxygen.tiki.org and make sure to add a redirect 301 for search engines
Also: http://fossies.org/dox/tiki-9.1/
1.1.3. phpDocumentor
Is it worth setting it up?
1.1.4. Dogfood TRIM
All our Domains and the Pre-Dogfood Server should be managed with TRIM
1.1.5. Round Robin / Redundancy / Disaster planning for all *.tiki.org content
TRIM handles backups so offsite backups are inherent. Not as important to have Round Robin / Redundancy / Disaster planning for all *.tiki.org content.
1.1.6. Setup a monitoring solution
- Uptime
- http://dev.tiki.org/tiki-admin.php?page=performance for warnings like -> Small amount of memory allocated to APC. Verify the configuration. The values to increase are apc.shm_size (for APC) or xcache.size (for XCache).
- Monitor for broken links. Ideally, we'd have this in Tiki
1.1.7. Implement Single Sign On (SSO) on 6 main sites.
This will likely be done after we move to suite.tiki.org for OpenLDAP. And then, we can set up CAS.
1.1.8. Code stats
- Figure out svnplot
1.1.9. Community Mail Server
This will move to suite.tiki.org.
Community Mail Server evolution. We also need to merge @tiki.org usernames with the emails.
Related links