Most Tiki installations are on Linux-Apache-MySQL-PHP. However, Tiki runs on more than just Linux. You can run it anywhere PHP can run. However, it is not as well tested and you may run into minor issues.

Starting with 5.x, Tiki is available in the Microsoft Web App Gallery at:
http://www.microsoft.com/web/gallery/Tiki.aspx
The installation is automated and generally reliable.

Related: Database Independence, Browser Compatibility

Windows compatibility project

Who

  • Greg Martin
  • Marc Laporte
  • Jimmy Gilbert
  • Chris Tingle
  • You? We are looking for volunteers.



What

  1. A large number proportion of forum posts are related to IIS or Windows hosting issues and many more are reported below.
  2. It is thought that most are various symptoms of a small number of real issues. These issues are presumed easy to fix. These problems are typically path issues. This apparently was working well in 1.9.x and possibly some problems appeared in 2.x. So we should test side by side 1.9.x, 2.x and 3.x to detect issues.
  3. Most of the active developers in Tiki use Linux and thus Windows issues are not naturally detected and solved.
  4. There are various hacks/recipes to make Tiki work in various environments. These should be checked and added to the main code base.


Why

Some corporate environments require that web apps run on Windows. So, in these cases, adding a LAMP server is not practical. Tiki gains to have higher adoption by working on more platforms.

Priorities

Please re-order this list! (It's just a first draft for now)

  1. WinXP + XAMPP works Install Tiki on XAMPP
  2. WinXP + EasyPHP works (Windows Local Install EasyPhp

  1. Win2008 Server, Apache, MySQL
  2. Win2008 Server, IIS, MySQL Windows Server Install
  3. Win2003 Server, IIS, MySQL (I submit that with Xampp there is already a workable solution for Apache)
  4. Win2003 Server, Apache, MySQL (seems to work fine)
  5. Standard shared Windows hosting like GoDaddy, etc.


http://tiki.org/tiki-browse_categories.php?parentId=70

Keep web.config and .htaccess synchronized

The web_config file for IIS needs to be kept in sync with _htaccess (for Apache). Most modifications are done to htaccess.

To convert rules from Apache to IIS, see Importing Apache mod_rewrite Rules if you're on Windows and Translate .htaccess Content to IIS web.config for examples.

If you are adding (or otherwise modifying the configuration) for one of the servers and can't do it for the other, add an entry here pointing to your commit that needs to be ported to the other server.


Starting in Tiki11, with route.php, this will become trivial.

Microsoft provides for automatic installs of PHP, MySQL & Tiki. We maintain the Tiki install for them. It's a quick way to get running on IIS.


Improve the documentation

Specific Windows install guides should be made if necessary


Contest

http://www.phponwindows.ca/ftw/

TRIM via FTP

TRIM will work with FTP somewhere during the Summer of 2009. now works with FTP. This will be yet another thing to make it easier to manage Tiki on Windows.

Items on wishlist

Open

Pending

Closed


alias
Show PHP error messages