szurubooru.git/README.md, branch master Fork of Szurubooru with patches for running on a modern system sans Docker https://www.git.jakob.space/szurubooru.git/atom?h=master 2025-10-12T19:08:47Z Get rid of Docker artifacts 2025-10-12T19:08:47Z Jakob L. Kreuze zerodaysfordays@sdf.org 2025-10-12T19:08:47Z urn:sha1:838d80ce274e0634eddafc08bed6d5ba8e0403e1 doc: update for yt-dlp 2023-08-17T12:58:09Z Zak B. Elep zakame@zakame.net 2023-08-17T12:58:09Z urn:sha1:59c497e1689fe5ff1c09c1882c04d789f9e32918 doc: fix external link in README.md 2022-03-31T02:44:32Z Maksymilian Babarowski maksymilian@babarowski.pl 2022-03-21T13:24:40Z urn:sha1:929071ea1a57dfd8ba48d487b4465418b633a04c doc: clean up 2020-06-05T14:29:52Z Shyam Sunder sgsunder1@gmail.com 2020-06-05T14:29:52Z urn:sha1:4f46619b919e7810e0b87f63e0d8c1134260b7b9 Add pool tests 2020-05-05T02:12:54Z Ruin0x11 ipickering2@gmail.com 2020-05-05T02:12:54Z urn:sha1:5ca21f9e7f5447a2c7841c1317dbe8df01b04e97 server/posts/upload: Add youtube-dl functionality 2020-04-03T17:11:54Z Shyam Sunder sgsunder1@gmail.com 2020-04-02T20:17:26Z urn:sha1:99a69333e656fcbf7acf55f8593cf2a70781fc6d allows for video-based posts to be created by using youtube-dl on the server. Access is controlled with the 'uploads:use_downloader' permission. doc: moved documentation to a seperate folder 2019-08-05T23:20:41Z Shyam Sunder sgsunder1@gmail.com 2019-08-05T23:15:37Z urn:sha1:48e7eb10f1bc06fb07b8b14c91b036a12fbe367d docs: Moved confusing requirements to INSTALL-OLD.md 2019-04-21T16:40:39Z Shyam Sunder sgsunder1@gmail.com 2019-04-21T16:40:39Z urn:sha1:f36cdc8719c4419dd163f83b7e1b330683cc1e50 build: add Docker functionality and documentation 2018-07-25T11:39:57Z Shyam Sunder sgsunder1@gmail.com 2018-07-12T03:30:13Z urn:sha1:6a6c4dc822344df01af0b3849083bc3ceda148e9 server/auth: add token authentication 2018-03-25T20:23:29Z ReAnzu anzu@reanzu.com 2018-02-25T10:44:02Z urn:sha1:2a69f0193f9e5aa451e0dbcb8c89070f3e49ffa5 * Users are only authenticated against their password on login, and to retrieve a token * Passwords are wiped from the GUI frontend and cookies after login and token retrieval * Tokens are revoked at the end of the session/logout * If the user chooses the "remember me" option, the token is stored in the cookie * Tokens correctly delete themselves on logout * Tokens can expire at user-specified date * Tokens have their last usage time * Tokens can have user defined descriptions * Users can manage login tokens in their account settings