Bug #7266
closed
Update documentation to use rudder-server-relay package instead of manual configuration
Added by Janos Mattyasovszky about 9 years ago.
Updated almost 9 years ago.
Description
Hi,
The Documentation in section "10.6.1. Installation procedure - On the relay" shows an outdated config, it's missing:
<IfVersion < 2.4>
Order deny,allow
Allow From all
</IfVersion>
<IfVersion >= 2.4>
Require all granted
</IfVersion>
- Assignee set to Vincent MEMBRÉ
- Priority changed from N/A to 1 (highest)
- Target version set to 3.0.10
Thank you for reporting the issue and the proposed solution !
Are you using 3.0 ? we created packages for relay server : rudder-server-relay, the config installed by that package is already apache 2.4 ready (maybe not the authorized network issue that was suggested in another issue ...)
I thought we already changed the documentation to explain this, I'm sorry about this and this should be fixed asap
- Target version changed from 3.0.10 to 3.0.11
- Target version changed from 3.0.11 to 3.0.12
- Assignee changed from Vincent MEMBRÉ to Alexis Mousset
- Target version changed from 3.0.12 to 3.0.13
- Status changed from New to In progress
- Subject changed from Relay's vhost config not apache 2.4 ready to Update documentation to use rudder-server-relay package instead of manual configuration
- Status changed from In progress to New
- Status changed from New to Pending technical review
- Assignee changed from Alexis Mousset to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-doc/pull/140
I don't think we need to change the 2.11 doc for apache 2.4 as the supported OSes do not provide it.
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Related to Bug #6226: Document migration from manually installed relays added
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.13, 3.1.6 and 3.2.0 which were released today.
Also available in: Atom
PDF