szurubooru-client

Frontend container for Szurubooru, an image board engine for small and medium communities

  • Media Applications
  • Tools & Utilities
Frontend container for Szurubooru, an image board engine for small and medium communities

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

16/100 Low

Maintained
16last commit 568 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 7 days ago

GitHub stars
0
Open issues
0
Last commit
2025-03-23
License
MIT
Activity
stale

Checked 5 days ago - source: GitHub (eadgbear/szurubooru-client)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 14 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set the config and data folders first In the server config file, set a strong secret key and point data_url/data_dir to the folders you want to use, because skipping this can make Szurubooru use an unsafe secret or store images in a confusing place. source
  • Start the database, then all containers Run `docker compose up -d sql` first, then `docker compose up -d` to start everything, because the app can fail or miss first-run setup if it starts before the database is ready. source
  • Create an admin account after startup After the containers are running, create an administrator account with the `szuru-admin` command and reset its password, because without an admin you cannot manage users or finish board setup. source

Fetched 14 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to start the database before the app containers?

Yes. Run docker compose up -d sql first, then start the rest with docker compose up -d. Starting the app before the database is ready can cause first-run failures.

How do I choose where images are stored?

Point data_url and data_dir in the server config to the folders you want to use. The source also recommends setting a strong secret key before first run.

How do I create the initial administrator account?

Create it after startup with the szuru-admin command and reset its password. Without an admin you cannot manage users or finish board setup.

Which ports should I expect in a Docker setup?

The API is commonly on port 6666 and PostgreSQL on 5432. You can set a custom port in the .env file, such as 8080.

Can I install szurubooru-client from Unraid Community Apps?

Yes. It is listed for Unraid and can be installed from your server with Community Apps.

Answers sourced from ca.unraid.net, context7.com, github.com, www.reddit.com

Community

Collected 13 days ago - public community threads