Thema
#postgresql
Loots, Blogposts und verwandte Themen rund um diesen Tag. Folge dem Tag, damit passende Updates in deinem Orbit bleiben.
2Gezeigte Loots
1Gezeigte Artikel
8Verlinkte Nachbar-Tags
Anschluss-Themen
Wenn du tiefer einsteigen willst, helfen die benachbarten Tags beim Vergleichen und Querlesen.
Loot
Mehr aus diesem Thema
Text: AI-generated
AI-generated · Automatically published by LinkLoot. DBJoy is a native SwiftUI PostgreSQL client that lets you query data conversationally, browse schemas visually, and manage connections with SSH tunnels—all while keeping writes locked behind explicit approval. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it does DBJoy is an AI-first PostgreSQL client built specifically for macOS. Instead of writing SQL from scratch, you can ask questions about your data in plain language (⌘J) and get answers backed by real queries executed against your database. The assistant looks up table structures automatically, runs the necessary queries, and shows results inline within the chat interface. Beyond conversational querying, DBJoy provides a full-featured database environment: schema browsing with visual ER diagrams, foreign key relationship mapping, paged data grids with column sorting, batch editing capabilities, and export options. It ships self-contained with libpq and pgdump bundled inside the app, so there's no separate dependency installation required. The tool also functions as an MCP server, allowing Claude Code and other AI clients to access your saved database connections for read-only lookups using DBJoy's stored credentials and SSH tunnel configurations. Who it helps macOS developers and data analysts who work primarily with PostgreSQL and want faster insight without constantly switching between terminal, GUI clients, and documentation. Particularly useful for teams where not everyone writes fluent SQL but needs reliable data answers. Also valuable for engineers managing multiple environments (local, development, staging, production) who need quick connection switching with proper security boundaries. Getting started Download the latest DBJoy-.dmg from the GitHub Releases page. Open the disk image and drag DBJoy to your Applications folder. Builds are signed with a Developer ID and notarized by Apple, so Gatekeeper won't block launch. To enable the AI features, navigate to Settings → AI Assistant and provide your own Anthropic or OpenAI API key. Keys are stored securely in the macOS Keychain rather than plaintext config files. Add database connections via pasteable connection strings (postgres://user:pass@host:5432/db) or manual entry; organize them into folders tagged by environment. For databases behind firewalls, configure SSH tunnels directly in the connection form—supports agent forwarding, private keys, or password authentication. Limits and costs Read-only by default: all assistant-generated queries execute in read-only transactions. To allow INSERT/UPDATE/DELETE operations, you must explicitly toggle Allow the assistant to change data per connection. Even when enabled, each modification requires an approval step before execution, and this feature is always disabled on production connections and never available on read-only-enforced connections. Requires your own API key for AI functionality; DBJoy itself is free under MIT license, but usage depends on your provider's token pricing. Currently PostgreSQL only, though the README notes "more database engines can be added." No hosted service exists—this is purely a desktop application requiring local Mac hardware. Source links Official repository Project documentation MIT License
- LinkLoot access
- Free
- Provider costs
- Unknown
Review open
Text: AI-generated
AI-generated · Automatically published by LinkLoot. A proxy that authenticates clients using their existing Tailscale identity, eliminating shared database passwords while supporting PostgreSQL and ClickHouse in a single process. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it does tailscale-database-gateway is a proxy that lets users connect to databases without managing individual credentials. It authenticates incoming connections based on the caller's Tailscale identity and application grants, then connects to the upstream database using either a username/password from a file or temporary credentials issued by HashiCorp Vault. The gateway supports three protocols in one process: PostgreSQL, ClickHouse native TCP, and ClickHouse HTTP. This means teams running mixed analytics and transactional workloads don't need separate proxies for each system. Who it helps Platform engineers and database administrators who want to eliminate password sprawl across development, staging, and production environments. If your team already uses Tailscale for secure networking, this tool extends that identity layer to database access control—no additional authentication infrastructure required. It's particularly useful when you need role-based access (like read-only vs. write permissions) mapped to specific applications or users, enforced at the network layer rather than relying on database-level user management alone. Getting started Deploy the published container image (ghcr.io/dialohq/tailscale-database-gateway) with Docker, Kubernetes, or any OCI runtime. You'll need: A Tailscale auth key from your admin console so the gateway can join your tailnet Your database hostname, port, name, username, and password—the login must already have the SQL privileges you want clients to use Access to edit your tailnet policy to grant clients reachability to the gateway on port 5432 and assign them capabilities like example.com/cap/postgres For basic setups, store database credentials in a JSON file mounted inside the container. For advanced scenarios, configure Vault's database secrets engine with dynamic roles and policies, then set vaultroles instead of credentialfiles in your configuration. Both a config file and environment variables are required; see the project documentation for variable names and example configurations. Limits and costs The gateway itself is MIT-licensed open source, but hosting costs depend entirely on your infrastructure choices. Running the container alongside your existing Tailscale setup adds no per-user licensing fees, though compute resources and storage for logs apply. Database certificate verification defaults to the container's built-in CA bundle. If your database uses a private CA, you'll need to mount its certificate manually and update the connection string. Role names like readonly map to upstream credentials you provide—the gateway doesn't create database permissions automatically. Ensure your configured logins have appropriate SQL privileges before exposing them through the proxy. Source links Official repository Project documentation MIT License
- LinkLoot access
- Free
- Provider costs
- Unknown
Review open
Blog