Project

General

Profile

Actions

User story #3009

closed

Create a usage handbook that summarize common usage scenarios in Rudder

Added by Matthieu CERDA over 11 years ago. Updated about 9 years ago.

Status:
Released
Priority:
2
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 PERRON2012-11-13Actions
Actions #1

Updated by Matthieu CERDA over 11 years ago

  • 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.

Actions #2

Updated by Nicolas CHARLES over 11 years ago

  • 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

Actions #3

Updated by Nicolas CHARLES over 11 years ago

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

This is much better, thank you Matthieu !

Actions #4

Updated by Matthieu CERDA over 11 years ago

You're welcome ! Thanks for the tips.

Actions #5

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from Pending technical review to 10
Actions #6

Updated by François ARMAND over 11 years ago

  • Description updated (diff)
Actions #7

Updated by Jonathan CLARKE over 11 years ago

  • Target version changed from 2.4.0~rc1 to 2.4.0~rc2
Actions #8

Updated by Jonathan CLARKE over 11 years ago

  • Assignee changed from Matthieu CERDA to Jonathan CLARKE
Actions #9

Updated by Jonathan CLARKE over 11 years ago

  • Target version changed from 2.4.0~rc2 to 2.4.0
Actions #10

Updated by François ARMAND over 11 years ago

  • Status changed from 10 to 15
Actions #11

Updated by François ARMAND over 11 years ago

  • Status changed from 15 to 10
Actions #12

Updated by Jonathan CLARKE over 11 years ago

  • Target version changed from 2.4.0 to 61
Actions #13

Updated by François ARMAND over 11 years ago

  • Target version changed from 61 to 2.4.2
Actions #14

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.2 to 2.4.3
Actions #15

Updated by Matthieu CERDA about 11 years ago

  • Target version changed from 2.4.3 to 2.4.4
Actions #16

Updated by Nicolas CHARLES about 11 years ago

Jon, could you review this doc please ?

Actions #17

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.4 to 2.4.5
Actions #18

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.4.5 to 2.4.6
Actions #19

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.4.6 to 2.4.7
Actions #20

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions #21

Updated by Jonathan CLARKE over 10 years ago

  • Status changed from 10 to Pending release
Actions #22

Updated by Nicolas PERRON over 10 years ago

  • Status changed from Pending release to Released

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

Actions #23

Updated by Benoît PECCATTE about 9 years ago

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

Also available in: Atom PDF