Project

General

Profile

Actions

User story #3009

closed

Create a usage handbook that summarize common usage scenarios in Rudder

User story #3009: Create a usage handbook that summarize common usage scenarios in Rudder

Added by Matthieu CERDA about 13 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
2
Assignee:
Jonathan CLARKE
Category:
Documentation
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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


Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #2989: Enhance the documentation: Add a note about making a VACUUM FULL in the database in case of a massive report archivingRejectedNicolas PERRONActions

Updated by Matthieu CERDA about 13 years ago Actions #1

  • Status changed from New to Pending technical review
  • % Done changed from 20 to 100

https://github.com/Normation/rudder-doc/pull/1 Pull request waiting for review.

Updated by Nicolas CHARLES about 13 years ago Actions #2

  • 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

Updated by Nicolas CHARLES about 13 years ago Actions #3

  • Status changed from In progress to Pending technical review
  • % Done changed from 90 to 100

This is much better, thank you Matthieu !

Updated by Matthieu CERDA about 13 years ago Actions #4

You're welcome ! Thanks for the tips.

Updated by Nicolas CHARLES about 13 years ago Actions #5

  • Status changed from Pending technical review to 10

Updated by François ARMAND about 13 years ago Actions #6

  • Description updated (diff)

Updated by Jonathan CLARKE about 13 years ago Actions #7

  • Target version changed from 2.4.0~rc1 to 2.4.0~rc2

Updated by Jonathan CLARKE about 13 years ago Actions #8

  • Assignee changed from Matthieu CERDA to Jonathan CLARKE

Updated by Jonathan CLARKE about 13 years ago Actions #9

  • Target version changed from 2.4.0~rc2 to 2.4.0

Updated by François ARMAND about 13 years ago Actions #10

  • Status changed from 10 to 15

Updated by François ARMAND about 13 years ago Actions #11

  • Status changed from 15 to 10

Updated by Jonathan CLARKE about 13 years ago Actions #12

  • Target version changed from 2.4.0 to 61

Updated by François ARMAND about 13 years ago Actions #13

  • Target version changed from 61 to 2.4.2

Updated by Nicolas PERRON about 13 years ago Actions #14

  • Target version changed from 2.4.2 to 2.4.3

Updated by Matthieu CERDA about 13 years ago Actions #15

  • Target version changed from 2.4.3 to 2.4.4

Updated by Nicolas CHARLES almost 13 years ago Actions #16

Jon, could you review this doc please ?

Updated by Nicolas PERRON almost 13 years ago Actions #17

  • Target version changed from 2.4.4 to 2.4.5

Updated by Nicolas PERRON almost 13 years ago Actions #18

  • Target version changed from 2.4.5 to 2.4.6

Updated by Nicolas PERRON over 12 years ago Actions #19

  • Target version changed from 2.4.6 to 2.4.7

Updated by Nicolas PERRON over 12 years ago Actions #20

  • Target version changed from 2.4.7 to 2.4.8

Updated by Jonathan CLARKE over 12 years ago Actions #21

  • Status changed from 10 to Pending release

Updated by Nicolas PERRON over 12 years ago Actions #22

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.4.8, which was released today.
Check out:

Updated by Benoît PECCATTE almost 11 years ago Actions #23

  • Project changed from 30 to Rudder
  • Category set to Documentation
Actions

Also available in: PDF Atom