Updates templates (auto-generated, on 10-Oct-2026)

This commit is contained in:
Liss-Bot committed 2026-10-10 20:59:32 +00:00
1 parent 9dd0d203ef
commit ff6d12a3ef
1 file changed
+35 -12
+35 -12
View File
@@ -13786,28 +13786,51 @@
"id": 354
},
{
"type": 1,
"title": "LibreDB Studio",
"name": "libredb-studio",
"description": "Self-hosted database IDE you use from a browser, covering twenty-eight engines - PostgreSQL, MySQL, Oracle, SQL Server, MongoDB, Redis, ClickHouse, Cassandra, Elasticsearch and more - with a schema browser and query history on all of them, and ER diagrams and EXPLAIN plans wherever the engine declares keys or returns a plan. Source: https://github.com/libredb/libredb-studio",
"categories": [
"Database",
"Tools"
"Tools",
"Development"
],
"description": "Web-based SQL IDE for sixteen database engines, with a schema browser, ER diagrams and query history. Source: https://github.com/libredb/libredb-studio",
"env": [],
"image": "ghcr.io/libredb/libredb-studio:latest",
"logo": "https://avatars.githubusercontent.com/u/251081537",
"name": "libredb-studio",
"note": "On first run LibreDB Studio generates the admin password and writes it once to the container logs (<code>docker logs libredb-studio</code>). Sign in as <code>admin@libredb.org</code> with that password. Connections and query history are kept in the <code>/app/data</code> volume. Reaching it over plain HTTP on a LAN address needs <code>AUTH_COOKIE_SECURE=false</code>, otherwise login fails while the container stays healthy.",
"platform": "linux",
"ports": [
"3000:3000/tcp"
],
"logo": "https://raw.githubusercontent.com/libredb/libredb-studio/main/public/logo.svg",
"image": "ghcr.io/libredb/libredb-studio:latest",
"restart_policy": "unless-stopped",
"title": "LibreDB Studio",
"type": 1,
"ports": [
"3006:3000/tcp"
],
"volumes": [
{
"container": "/app/data"
}
],
"env": [
{
"name": "AUTH_COOKIE_SECURE",
"label": "Reached over plain HTTP, with no HTTPS in front",
"description": "Leave it false to reach the app at http://your-host:3006. Without it the session cookie is marked Secure, the browser throws it away over plain HTTP, and sign-in returns you to the login page while the container stays healthy. The cookie then travels in cleartext, so keep it to a trusted network and set this to true once a reverse proxy puts HTTPS in front.",
"default": "false"
},
{
"name": "STORAGE_PROVIDER",
"label": "Where saved connections are kept",
"description": "sqlite keeps them in the volume below, so they survive the container being recreated. The alternatives are local, which keeps them in the browser instead, so a volume backup holds none of them, and postgres for a shared server.",
"default": "sqlite",
"preset": true
},
{
"name": "STORAGE_SQLITE_PATH",
"label": "Path of that SQLite file",
"description": "Inside the volume, so it persists.",
"default": "/app/data/libredb-storage.db",
"preset": true
}
],
"note": "Open <code>http://&lt;your-host&gt;:3006</code>. On the first start the app creates the admin account <code>admin@libredb.org</code>, generates its password and its signing secret, and prints the password to the container log, so read the log before signing in. Both are kept in <code>/app/data</code> and reused on later starts, which is why setting <code>ADMIN_PASSWORD</code> on its own afterwards does not change the stored one: to replace it, set <code>ADMIN_PASSWORD</code> to the new value and <code>ADMIN_PASSWORD_RESET=true</code> together for one start, then remove the flag. Saved connections, query history and the app's SQLite file all live under <code>/app/data</code>, which the volume covers. The databases you connect to are not part of this template, which runs LibreDB Studio alone. MIT licensed, no paid tier. Docs: <a href=\"https://libredb.org\">libredb.org</a>",
"maintainer": "https://github.com/libredb/libredb-studio/",
"id": 355
},
{