WIKI - one backend engine, several frontends - how?

Question

PHP

Dano is a domain with a wiki engine (which one I'm considering, probably media-wiki). Start page (primitive, not the question), directing to several subdomains (site1.domain.net, site2.domain.net, etc)
On subdomains, you need to deploy various wikis - different in content , layout, templates, flooded pictures.
What is the most economical way to deploy such a system? Why not keep a copy of the engine for each subdomain? :)
Restrictions: virtual hosting, the number of subdomains-subwikis should not be strictly limited: if you want - deploy another one, if you want - demolished. The engine is probably media-wiki, but not sure.

Answer 1

Your subdomains are separate folders (virtual hosts), right?
Let's say you have the engine files in /var/www/host1/core/, and the site configs (database connection, etc.) in /var/www/host1/config
We shift the engine code somewhere in /var/www/my_engine_core/and create symbolic links
If my memory serves me , there should be something like

ln -s -T /var/www/my_engine_core/ /var/www/host1/core/
ln -s -T /var/www/my_engine_core/ /var/www/host2/core/

etc
Well, of course, you still need to correctly configure the access rights, folder owners, and so on.

Answer 2

I didn't use media-wiki, so I can't speak for this engine. I know (and used) WordPress in multisite mode. On one copy of the engine, you can create an unlimited number of sites both on subdomains (sub.domain.net) and in subdirectories (domain.net/sub). For WordPress, there are extensions for organizing Wiki, so in terms of functionality, you can pull WP up to what you need. Of course, for a WordPress multisite, it is recommended to use a server, but for a small load, at first, a virtual one will do.