Where should a system administrator store documentation and server configs, as well as his own observations and thoughts?

Question

Documentation

Hello. Sysadmins, where do you keep documentation on setting up servers? And do you store the sequence of actions when setting up your servers, configs and personal observations?
update: I myself keep configs and documentation in text files, passwords in keepass2 and plus btsync sync to read it on all my devices.

Answer 1

I will answer according to the documentation...
1. Format.
It is better for you to do this in plain text, because even being in the console, you can always read them.
Formats: any of .md, .rst, asciidoc (because it is possible to render them in pretty format) inside various systems.
2. Storage
The storage method is SCM only (which one: git, svn, hg or older - I don't know what you are using). Let me explain why not the file system:
- it is important for you to know the state of your equipment at a certain moment. Those. you can always look at the configuration that was current a month or two ago and identify problems.
- you can always diff and see the changes. Often, this should be done not just now, but "suddenly" :)
I STRONGLY DO NOT recommend using atlassian confluence, as they say above, for your tasks. Reason:
- you are tied to a vendor (even for 10 bucks for a min. license). If you drop the vendor you will NOT be able to get it - just copy/paste or buy plugins for hundreds of bucks.
- Atlassian's markup is hard-coded into the software. You can't upload wiki markup there (except when buying hundreds of bucks plugins like scroll)
- and best of all, you can't view text in the console!
3. Visualization
It all depends on the amount of time you are willing to spend. I know there are md rendering solutions for a normal wiki. Here you better google the best option for the previous two points.

Answer 2

I actively use Onenote now, it's convenient.
When I worked with Linux, I stored it in text files in md-format, I kept my blog.

Answer 3

I use Zim desktop - wiki application, very convenient.
Alternatively, BitBucket is a personal storage..

Answer 4

Paper will endure everything :)
In general, Google Keep.

Answer 5

tekstovichki-blogiki-sveenochki, no? :)

Answer 6

private git

Answer 7

Passwords - in KeePass, the database of which is stored on the TrueCrypt cryptocontainer :-)
Configs - in Subversion.
Notes and more - in a cozy blog: at-hacker.in

Answer 8

wiki
ansible

Answer 9

Passwords Keepas
configs txt and attach to the wiki
thoughts / docs - wiki
All this must be backed up somewhere remotely to the cloud or to a server / vps somewhere so that there are always 2+ instances in total.

Answer 10

atlassian confluence
cvs
one note

Answer 11

All configs, instructions, and so on, except for passwords, I store in a tree-like (very convenient for an IT-person) CherryTree editor.

Answer 12

Passwords - Safe-In-Cloud
Configs, entries, other - Evernote
Tasks - Wunderlist ( Toodledo as an option)
Quick Notes - Google Keep

Answer 13

Passwords in a text file - in an encrypted archive in the cloud
Notes - and tasks - todist (android + web) sycamore version very much good 1200 per year