Mediawiki VS fly_postgres_elixir

Wikipedia that runs on MediaWiki which is written in PHP. source code

MediaWiki

"https://ibb.co/0F2rWbG/logo.png", 'icon' => "https://ibb.co/0F2rWbG/logo.png",];## UPO means: this is also a user preference option$wgEnableEmail = true;$wgEnableUserEmail = true; # UPO$wgEmergencyContact = "";$wgPasswordSender = "";$wgEnotifUserTalk = false; # UPO$wgEnotifWatchlist = false; # UPO$wgEmailAuthentication = true;## Database settings$wgDBtype = "mysql";$wgDBserver = "wiki";$wgDBname = "wikipapadeluxe";$wgDBuser = "root";$wgDBpassword = "";# MySQL specific settings$wgDBprefix = "";# MySQL table options to use during installation or update$wgDBTableOptions = "ENGINE=InnoDB, DEFAULT CHARSET=binary";# Shared database table# This has no effect unless $wgSharedDB is also set.$wgSharedTables[] = "actor";## Shared memory settings$wgMainCacheType = CACHE_NONE;$wgMemCachedServers = [];## To enable image uploads, make sure the 'images' directory## is writable, then set this to true:$wgEnableUploads = false;#$wgUseImageMagick = true;#$wgImageMagickConvertCommand = "/usr/bin/convert";# InstantCommons allows wiki to use images from https://commons.wikimedia.org$wgUseInstantCommons = false;# Periodically send a pingback to https://www.mediawiki.org/ with basic data# about this MediaWiki instance. The Wikimedia Foundation shares this data# with MediaWiki developers to help guide future development efforts.$wgPingback = true;# Site language code, should be one of the list in ./includes/languages/data/Names.php$wgLanguageCode = "en";# Time zone$wgLocaltimezone = "Europe/Berlin";## Set $wgCacheDirectory to a writable directory on the web server## to make your wiki go slightly faster. The directory should not## be publicly accessible from the web.#$wgCacheDirectory = "$IP/cache";$wgSecretKey = "b564d730428f48d0882f0ae67283fc844ba41347848b4868501bdb524ff86342";# Changing this will log out all existing sessions.$wgAuthenticationTokenVersion = "1";# Site upgrade key. Must be set to a string (default provided) to turn on the# web installer while LocalSettings.php is in place$wgUpgradeKey = "d8e35fccd5b424df";## For attaching licensing metadata to pages, and displaying an## appropriate copyright notice / icon. GNU Free Documentation## License and Creative Commons licenses are supported so far.$wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright$wgRightsUrl = "";$wgRightsText = "";$wgRightsIcon = "";# Path to the GNU diff3 utility. Used for conflict resolution.$wgDiff3 = "";# The following permissions were set based on your choice in the installer$wgGroupPermissions['*']['edit'] = false;## Default skin: you can change the default skin. Use the internal symbolic## names, e.g. 'vector' or 'monobook':$wgDefaultSkin = "vector";# Enabled skins.# The following skins were automatically enabled:wfLoadSkin( 'MinervaNeue' );wfLoadSkin( 'MonoBook' );wfLoadSkin( 'Timeless' );wfLoadSkin( 'Vector' );# End of automatically generated settings.# Add more configuration options below.

Do you mean Fandom wiki? You would want some kind of open source wiki platform. MediaWiki (used for Wikipedia) is probably the most popular and full featured.

It's all open source https://github.com/wikimedia/mediawiki

A little money, a little installation work, and this: https://github.com/wikimedia/mediawiki

This is overkill. The entirety of Wikipedia is made available for free download by the Wikimedia foundation, the code is open-source, and anyone can set up their own copy of Wikipedia on a normal PC with a big hard disk. Power this off a portable battery and solar panel and you have off-grid Wikipedia without any hardware hacking.

Last time I had occasion to use one - i used mediawiki

https://github.com/superfly/fly_postgres_elixir

It does this by sending writes to the primary region over RPC (via distributed elixir). The write is performed on a primary instance adjacent to the DB, then the result, and the postgres log-sequence-number, is sent back to the remote node. When the library gets a result of the RPC write, it blocks locally until its local read replica matches an LSN >= write LSN, then the result is returned to the caller

This gives us read-your-own-writes for the end-user, and the calling code remains unchanged for standard code paths. This doesn't solve all classes of race conditions – for example you may broadcast a message over Phoenix.PubSub that causes a read on the remote node for data that isn't yet replicated, but typically you'd avoid an N query problem from pubsub in general by populating the data in the message on the publisher beforehand.

There's no completely avoiding the fact you have a distributed system where the speed of light matters, but it's Fly's (and Phoenix's) goal to push those concerns back as far as possible. For read heavy apps, or apps that use caching layers for reads, developers already face these kinds of problems. If you think of your read-replicas as cache with a convenient SQL interface, you can avoid most foot guns.

I'm happy to answer other questions as it relates to Phoenix, Fly or what Phoenix + Fly enables from my perspective.