Brainstorming

Welcome to brainstorming page, where User:Diskette and other people brainstorms for upcoming features and infrastructure planning. And also Rubberducking

The wikifarm infrastructure

The best way to manage stuff is to make a "centralized" wiki and connect all other wikis into that central wiki. The central wiki has to provide "basic" templates like all the boxes (e.g., Infoboxes, message boxes) and then synchronizing those templates to other wikis.

The *nix wikis compared to others

This "central" wiki provides basic templates that could be used in other wikis, Commons-like image storage, a rule page, and it acts sort of like a "global" blocks to trolls. But there's some problem to this, which includes localization, and other wikis needs something a little different. But mainly, *nix wiki needs Templates, Wikimedia Commons-like image storage, and a rule. On other wiki, such as the planned JzBoy wiki needs needs Template, but what about Wikimedia Commons-like image store? Or a rule? Well, I think JzBoy wiki should be able to use the central wiki images, but not strictly upload to it since the images used would probably be licensed under some license that Mr. JzBoy himself allows.

Features	*nix wiki	JzWiki
Basic templates	Yes	Yes
Commons-like image storage	Yes	One-way only
Global rule page	Yes	Yes (You agree to reading the whatever this centralized wiki will be called's rules and JzBoy wiki rules)
Account management...ish?? (Keycloak already does this)	Yes	Yes

Authentication service

Currently, there are two ways to do authentication service. The first one is to use the the Central Auth Extension or use the more flexible and extensible OpenID Connect via Keycloak.

Feature matrix

Features	Central Auth	OpenID Connect
Can I connect multiple wikis?	Yes	Yes
Can I connect it to another unrelated service?	Yes (via OAuth Extension)	Yes
Can it be authorized by other service?	Yes... via the OpenID Connect Extension itself	Yes

Okay, I just realized mid-way... why not use both for the authentication service? But there's also two ways to do this

Features	Central Auth first, OpenID for SSO	OpenID first, Central Auth as an anti-account conflict
Description	Connecting all Wiki as a family wiki (An already mandatory work), one wiki is an authentication wiki and to log-in using other services, configure OpenID for other services	Configure OpenID Extension to connect to the central Keycloak account management, configure Keycloak for other services SSO as well.

Actually, Central Auth requires me to do Wiki Family

Wiki family vs Normal installation

Wiki family is a little be cumbersome to install, but is easier to do in the long run

Container policy

Every service in Thetic needs to be on container, as container stores all the data on the ZFS drives, with one drive fault tolerance.