User story #3009
closed
Create a usage handbook that summarize common usage scenarios in Rudder
Added by Matthieu CERDA about 12 years ago.
Updated over 9 years ago.
Description
Create a usage handbook that summarize common usage scenarios in Rudder, like:
- Database management
- Backup procedures
- Application tuning ...
This ticket is both the "meta ticket" and the implementation one, since for documentation, we don't have to integrate with other part of Rudder.
Pull request: https://github.com/Normation/rudder-doc/pull/1
- Status changed from New to Pending technical review
- % Done changed from 20 to 100
- Status changed from Pending technical review to In progress
- % Done changed from 100 to 90
Matthieu, I've made some remarks in the pull request, to explain better was is VACUUM and VACUUM FULL
Could you adress this ?
Thank you
- Status changed from In progress to Pending technical review
- % Done changed from 90 to 100
This is much better, thank you Matthieu !
You're welcome ! Thanks for the tips.
- Status changed from Pending technical review to 10
- Description updated (diff)
- Target version changed from 2.4.0~rc1 to 2.4.0~rc2
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- Target version changed from 2.4.0~rc2 to 2.4.0
- Status changed from 10 to 15
- Status changed from 15 to 10
- Target version changed from 2.4.0 to 61
- Target version changed from 61 to 2.4.2
- Target version changed from 2.4.2 to 2.4.3
- Target version changed from 2.4.3 to 2.4.4
Jon, could you review this doc please ?
- Target version changed from 2.4.4 to 2.4.5
- Target version changed from 2.4.5 to 2.4.6
- Target version changed from 2.4.6 to 2.4.7
- Target version changed from 2.4.7 to 2.4.8
- Status changed from 10 to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.4.8, which was released today.
Check out:
- Project changed from 30 to Rudder
- Category set to Documentation
Also available in: Atom
PDF