hanyuu/hanyuu.cfg.example

database:dsn mariadb://user:pass@host/database?charset=utf8mb4

site:name Hanyuu

;sentry:dsn sentry dsn here

misuzu:endpoint http://msz.local
misuzu:secret   beans

oauth2:device:verification_uri          https://hau.local/oauth2/verify
oauth2:device:verification_uri_complete https://hau.local/oauth2/verify?code=%s

csrfp:secret change this please
Added example config file. 2024-07-20 19:31:15 +00:00			`database:dsn mariadb://user:pass@host/database?charset=utf8mb4`

			`site:name Hanyuu`

Forgor the one for Sentry. 2024-07-20 19:32:19 +00:00			`;sentry:dsn sentry dsn here`

Added example config file. 2024-07-20 19:31:15 +00:00			`misuzu:endpoint http://msz.local`
			`misuzu:secret beans`

Removed mentions of "device" from the UI and URLs. While the intention of the extension specification to OAuth2 for device codes is indeed intended for handling authorisation on devices where the user cannot use any input method on the device, it's also very useful for when we want to authorise older devices where there are other difficulties, such as outdated or intentionally omitted root certificates making it only possible to use plain HTTP, or just other sorts of applications where having to make a web UI just for receiving the authorisation code to complete the token request would be a bother, for me such a case would be bots like Satori. It essentially just replaces three-legged authorisation from OAuth 1.0a but without the needlessly complex annoying aspects of OAuth 1.0a. Beyond that I'm also just sick of entering my ridiculously long, randomly generated password letter by letter on the inaccurate touch screen of the Nintendo 3DS. 2024-07-30 13:08:22 +00:00			`oauth2:device:verification_uri https://hau.local/oauth2/verify`
			`oauth2:device:verification_uri_complete https://hau.local/oauth2/verify?code=%s`
Added styling to the authorisation prompt etc. 2024-07-21 00:47:00 +00:00
			`csrfp:secret change this please`