Project

General

Profile

Actions

Feature #18785

open

Handle oudated/unclear/wrong howto's in a decent matter.

Added by Mischa The Evil about 9 years ago. Updated about 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Website (redmine.org)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

This came up while seeing yet another forum post referring to howtos which are outdated, confusing or just plain wrong (Continuing the problems - Application error Rails applic...). For this post I looked at the howto's available for installation on CentOS and a generic one for apache1 and only two seemed recently updated and clear about what its assumptions are and which components are used (Redmine_203_with_Subversion_and_LDAP_Authentication_(for_Redmine_and_Subversion_through_Redmine)_on_Centos_6_i386_-_detailed and Install_Redmine_25x_on_Centos_65_complete). All the others need (serious) work.

We need some way of management of the provided (installation) howtos. This can (in its simplest form) be a default type of infobox containing info about the Redmine version, used way of deployment (servers, app. servers, proxies etc.), used Rubies and their managers, etc. Ideally they could have a peer-review signature to optimize their overall quality, but such would require a lot of time.

Temporarily, we might be able to use a plain, colored table as used in Hooks_List. Some other ideas?

1 HowTo_install_Redmine_on_CentOS_5, HowTo_install_Redmine_on_CentOS_Detailed, How_to_Install_Redmine_on_CentOS_(Detailed), Redmine_on_CentOS_installation_HOWTO, RedmineAndSELinuxOnCentOS and HowTo_configure_Apache_to_run_Redmine.

Actions

Also available in: Atom PDF