[00:05:53] <superboot>	 Hi all. I'm looking to manage a mediawiki based internal knowledge-base. Does anyone have any documented workflow they can suggest? Fore example, running on Vagrent, or Docker, etc, something explaining the interactions of the tool stack used for development, testing, and pushing to production? 
[00:09:58] <PixDeVl>	 So an instance for like a company or something?
[00:10:12] <superboot>	 Yes.
[00:10:40] <superboot>	 Just wondering what others do, before I go re-inventing the wheel. :)
[00:10:40] <PixDeVl>	 Used by non tech users but not on the internet
[00:10:55] <superboot>	 Yes.
[00:10:57] <PixDeVl>	 I think maybe something like cansta(spelling?) may be good let me find the link
[00:11:37] <PixDeVl>	 https://www.mediawiki.org/wiki/Canasta
[00:11:49] <PixDeVl>	 Something like this superboot?
[00:12:07] <superboot>	 Let me check it.
[00:14:16] <superboot>	 Oh nice! That's a nice start! :)
[00:14:21] <superboot>	 Thanks!
[00:14:48] <p858snake|cloud>	 it all depends on the skill based the company has, and will likely to have if people depart, eg, If the it team already have strong linux skills, The packages provided by the operating system reposititories should probably be fine
[00:15:49] <PixDeVl>	 The internal company thing reminded me of [[BlueSpice]] but I think it's likely overkill. I've never used it but seems interesting
[00:18:31] <PixDeVl>	 p858snake|cloud Canasta is docker based with a CLI so it should be fine in case of a leave if you have someone who knows their way 'round the CLI