How to maintain documentation on servers (Sys.Administration)?

Question

iOS

Greetings, a small team of system administrators (3 people), there is a need to organize data storage by servers / clients (passwords, task histories, scripts, configs, etc.)
At the moment we store everything in text files. With the growth of the base, the disadvantages of this approach were revealed:
- Inconvenient search
- Inconvenient to exchange with each other
Ideally, this will probably be a simple CRM with code insertion, attachment of small files (pdf, txt) and access rights.
Prompt normal options, it is possible paid. Thank you.

Answer 1

Try adding another keyframes but prefixed with -webkit-

@-webkit-keyframes z_mob_phone_anim {
    ...
}

Answer 2

For passwords and other confidential information I use enpass.
The password database is encrypted and closed with a master password. Inside is a convenient tree structure. You can use cloud storage for synchronization between the team. Free for desktops.
As an alternative to open source KeePass , but I had to tinker with it to set up synchronization under Linux.

Answer 3

redmine?
UPD: Scripts and configs - in VCS. VCS to taste :) redmine supports all known ones - svn, git, mercurial...

Answer 4

Citycat is correct. Three different programs are needed to meet your needs. Tracker, perhaps with built-in functionality a la wiki. Redmine is quite suitable for this, yes. Alternatively, you can look at YouTrack. Up to 10 users free can use. But yutrek is a pure task tracker. There is no way to keep documentation.
Passwords -- you need to use a password manager. We use KeePass, it's not bad.
Storage of configs/scripts -- SVN. Some prefer git, but in my opinion, it is not suitable for storing configs. The mere need to drag the entire turnip locally to each server (i.e., all the configs of all servers) already calls into question the possibility of its use in this scenario. Yes, this is bypassed - you can pull out individual sections of turnips, but this is already dancing with a tambourine. SVN is much better for storing configs.
Yes, scripts can be stored anywhere. But from the point of view of infrastructure, I would not produce unnecessary entities, i.e. if you use SVN to store configs, then it is better to store scripts there.
At one time, we made a system for collecting and storing configs based on SVN, with auto-commits once a day and sending notifications about the changes made to the soap to everyone in the department. Moreover, the auto-commit was not sent, only notifications were sent for manual commits, i.e., where there were comments on the commits.
For documentation - any engine, for example, the same dokuwiki.
And about access to freelancers, they also correctly said - the freelancer is given a temporary account in the task tracker, temporary necessary accesses are issued, and when the task is closed, everything is cleared. If he needs some documents, then it's probably easier to export them to PDF and send them to him.

Answer 5

Maybe Evernote will do?

Answer 6

redmine and its wiki
ansible also partially solve this problem