Postgres12.5
PostgreSQL 12.5 is an Alpine-based, resource-light edition of the open-source object-relational database, distributed as a ready-to-run UNRAID community…
Platform availability
Available on 2 of 10 platforms
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.
8/100 Low
- Maintained
- 0GitHub repository no longer exists
- Popular
- No data
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 2 of 4 factors.
Availability: platform listings confirmed today
No GitHub repository data collected yet.
Checked today - source: GitHub (postgres/postgresql)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Container setup The PostgreSQL 12.5 container is configured interactively before first start: set the database username and password, default database name, and any optional arguments in the template's settings, as in a standard Docker PostgreSQL guide. source
- UNRAID Installation Install via the UNRAID Community Apps template (Postgres12.5). The template deploys a Dockerized PostgreSQL 12.5 server on your UNRAID host; after first start configure the superuser password and connection string in the container's environment or pg_hba.conf. source
Fetched yesterday - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does a Qlik installer flag PostgreSQL 12.5 as unsupported?
The source reports a Qlik installer warning that says PostgreSQL 12.5 is unsupported. It asks whether that warning is an error, but it does not confirm a final answer.
Should multiple self-hosted apps share one PostgreSQL deployment?
For self-hosting, the source recommends one database engine per app. It says this is especially appropriate when containerizing and orchestrating with Docker Compose.
How can a hobby project run redundant PostgreSQL?
One example uses three servers in three locations and providers. It keeps PostgreSQL as a critical service on smaller servers to provide redundancy.
Answers sourced from community.qlik.com, www.reddit.com, www.redditmedia.com
Community
Collected 48 days ago - public community threads