The wiki is self-hosted. It’s running as a container for security and inter-operability. Datas are stored externally on Raid5 storage and replicated on another location. A cold backup is scheduled to keep integrity.
Pros
The App is open-Source
Each documentation will have the same format
It'll be accessible easily anywhere in the world
Knowledge can be shared
Need (Excerpt Below)
Every project was documented on his own way. I wanted a way to unify this Knowledge base, search inside, co-editing and make it easily shareable.
Cons
I need to update and secure the app on my own
Interlink between DB and network need to be secure and well understood
Results
A web App available 24/7
Qualification & Production infrastructure under docker
Replication between both Infra + cold backup
Knowledge replicated on another geographical point
Multiple end-user to contribute to different topics
We needed to initiate some actions without remembering the setup each time we needed to access services. App should be easy to carry and provide easy access to actions.
I wanted to host and tests some apps before publishing/use it on internet. The physical server hosting are light, small and silent. The solution must not consume a lot of ressources.