Infrastructure Team
The Infrastructure Team is responsible for hosting, server administration, domains, uptime, etcTable of contents
- Release responsibilities
- Ongoing responsibilities
- Fix and close
- 1. transition from tikiwiki.org to tiki.org
- 2. Activate the removal of www for all sites
- 3. Clean up permissions on tiki.org
- 4. Images lost on dev.tw.o
- 5. Rewrite Rules
- 6. dev.tiki.org -> delete from user list all users that are not necessary here
- 7. Delete a pic
- 8. Move calendar data from dev to info site
- Major projects
- 1. Dogfood Forum and List Synchronization between tw.o forums and SourceForge Mailing Lists
- 2. Dogfood TRIM
- 3. Round Robin / Redundancy / Disaster planning for all *.tiki.org content
- 4. Help with sites revamp
- 5. Implement Single Sign On (SSO) on 6 main sites.
- 6. Code stats
- 7. Activate mindmap on some tiki.org sites
- 8. Community Mail Server
- Alias
Release responsibilities
- Progressively update all *.tiki.org sites to the new version. The ultimate DogFood!
- The goal is that all major sites are upgraded before it's released.
- Order is Branding, Themes, Documentation, Community, Development, Profiles, Info.
- The goal is that all major sites are upgraded before it's released.
- Monitor for broken links, performance regressions, etc.
- Update official version numbers up to date (which is where all the Tikis connect to know if they should update).
Ongoing responsibilities
This page is to coordinate work and list requests about various aspects of *.tiki.org sites and community toolsThis 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.
Do not put any security or sensitive info below. Instead, contact http://security.tiki.org
1. Hosting the *.tiki.org sites
- Monitoring uptime with help from AvonSys
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/statshtaccess
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?
3. Keep all sites up to date & making Intertiki work
- All our sites should kept in sync with proposed branch
-
Use sh doc/devtools/svnup.sh so footer is up to date.No longer necessary as Tiki code detects properly nowadays
4. Backups
- Each host should make send backups to another. Can be done by TRIM
5. Manage DNS, domain name and email accounts
- Managing the DNS info for the various Domains (changi)
- Hosting email MarcLaporte
- SSL (changi)
6. purge spammer accounts from tiki.org
These are accounts created but the email was not validated7. Maintain Pre-Dogfood server
Fix and close
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)
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/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.php4. Images lost on dev.tw.o
See here: http://dev.tiki.org/TrackerFieldUIRevampImage missing:
http://dev.tiki.org/img/wiki_up/trackerui1.png
and two images here: http://dev.tiki.org/Translation+Editor+Revamp
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)
5. Rewrite Rules
I posted a comment heresame problem with http://doc.tiki.org/calendar
dev is ok:
http://dev.tiki.org/categories
6. dev.tiki.org -> delete from user list all users that are not necessary here
http://dev.tiki.org/wish11287. Delete a pic
http://tiki.org/img/wiki_up//spiderdog_in_action.png8. Move calendar data from dev to info site
Check with Rick 1stWith a persistent rewrite rule . Now: Upcoming Events
Major projects
1. Dogfood Forum and List Synchronization between tw.o forums and SourceForge Mailing Lists
http://dev.tiki.org/wish22822. Dogfood TRIM
All our Domains and the Pre-Dogfood Server should be managed with TRIM3. 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.4. Help with sites revamp
5. 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.6. Code stats
- Figure out svnplot
7. Activate mindmap on some tiki.org sites
http://tiki.org/tiki-mindmap.phphttp://profiles.tiki.org/tiki-mindmap.php
http://dev.tiki.org/tiki-mindmap.php
http://doc.tiki.org/tiki-mindmap.php
Tiki bug or server issue?
8. Community Mail Server
This will move to suite.tiki.org.Community Mail Server evolution
