← Directory

Lemmy-Postgres

PostgreSQL database for Lemmy with automatic database upgrades.

  • Databases
PostgreSQL database for Lemmy with automatic database upgrades. It stores Lemmy data and helps self-hosted operators upgrade PostgreSQL with less manual work.

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS
  • 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.

74/100 Good

Maintained
100last commit 12 days ago
Popular
8314,614 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
404 GB minimum RAM, runs on ARM

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

GitHub stars
14,614
Open issues
128
Last commit
2026-10-01
Latest release
0.19.20
License
AGPL-3.0
Activity
declining

Checked 7 days ago - source: GitHub (LemmyNet/lemmy)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 2 CPU core(s), 50 GB disk. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Start PostgreSQL first Install and start PostgreSQL (for example with pacman, apt, or Homebrew); if the service errors, create the data folder, make it owned by the postgres user, and initialize it. Without a running database, Lemmy cannot save posts, comments, or accounts and the server will not start. source
  • Edit .env.local before first run Copy the example environment file to .env.local and fill in your site settings before starting Lemmy. Missing or wrong settings can make the site show errors, use the wrong database, or not reach you by your domain. source
  • Set your real domain in lemmy-ui Replace the placeholder example.com in the lemmy-ui service file (a system service file) with your actual domain and save it under /etc/systemd/system. If you leave the wrong host, the web front end may not connect to your server or HTTPS may not work properly. source

Fetched 14 days ago - each note links to its source

Alternatives (7)

  • Aether - Open source, self-governing communities with auditable moderation and mod elections.
  • Digg - Social news platform with topic-based communities, transparent moderation, user voting, content discovery, anti-spam measures, web and mobi…
  • Hacker News - Hacker News is a social news website that caters to programmers and entrepreneurs, delivering content related to computer science and entre…
  • Reddit - A social news website where content shared by users is voted on, organized into 'subreddits,' and can appear on the front page amid diverse…
  • Steemit - A non-censored social platform where users are incentivized to contribute and curate content.
  • Tildes - A non-profit community site driven by its users' interests.
  • Voyager - Voyager is a self-hostable, open-source web client for Lemmy, a federated link aggregator.

Checked 11 days ago - source: AlternativeTo

Common questions

Why does Lemmy fail to start or save posts if PostgreSQL is not working?

Start PostgreSQL first; if the service errors, create the data folder, make it owned by the postgres user, and initialize it. Without a running database, Lemmy cannot save posts, comments, or accounts and will not start.

What environment file needs to be prepared before the first Lemmy run?

Copy the example environment file to .env.local and fill in site settings before starting Lemmy. Missing or wrong settings can cause errors, make Lemmy use the wrong database, or prevent the site from being reachable by your domain.

What host setting can break HTTPS or the Lemmy web front end?

Replace the placeholder example.com in the lemmy-ui service file with your actual domain and save it under /etc/systemd/system. Leaving the wrong host can prevent the web front end from connecting to your server or make HTTPS not work properly.

Why might a remote Lemmy instance appear lagging in federation state?

Remote Lemmy instances send apub sync actions serially through the Lemmy queue. If your server processes them slower than the origin server sends them, the remote instance will show as lagging.

Answers sourced from github.com, github.com, github.com, join-lemmy.org

Community

Collected 14 days ago - public community threads