dumbtv
dumbtv가 ADB로 Fire TV에서 광고·추적·업데이트 알림을 제거, 루트·앱 변경 없이, 무료 오픈소스
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Self-hosted gateway for safe, audited access to production PostgreSQL and MySQL databases
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗A self-hosted gateway that lets engineers query production PostgreSQL and MySQL databases safely. Every statement is parsed, checked against the caller's access and the cluster's policy, rewritten with hard limits, executed in a guarded transaction, masked and audited. Engineers never see database credentials.
WITH x AS (DELETE …) SELECT …
is a write). Unsupported SQL fails closed.EXPLAIN cost gate, per-cluster concurrency limits, read
replica routing and server-side cancellation.SELECT *, leading-wildcard LIKE, non-sargable filters and large
OFFSETs, with one-click fixes such as a sample LIMIT or a preview of the
rows a write will touch. Suggestions never change what is allowed.| Overview | Clusters |
|---|---|
| Safety policy | Approvals |
With Docker Compose, choose an initial admin password and a stable master key (the server refuses to start without a valid 32-byte key):
export VDA_MASTER_KEY="$(openssl rand -base64 32)"
export VDA_BOOTSTRAP_ADMIN_PASSWORD='choose-a-long-random-password'
docker compose --profile demo up --build
Open http://localhost:8080 and sign in as [email protected]. The demo
profile starts PostgreSQL and MySQL databases with sample shop data; register
them in the console:
| Engine | Host | Port | Database | User | Password |
|---|---|---|---|---|---|
| PostgreSQL | demo-postgres | 5432 | shop | demo | demo-local-only |
| MySQL | demo-mysql | 3306 | shop | demo | demo-local-only |
Use the development environment for the demo; production defaults block writes.
Keep the master key in a secret manager and back it up with the metadata
database: stored credentials can't be decrypted with a different key.
To try the console without any backend, run the UI in mock mode:
cd web && npm ci && npm run dev:mock
| Topic | |
|---|---|
| Architecture | Components, data model, access model and query pipeline |
| Security model | Guarantees, defense-in-depth layers and known limits |
| Deployment | Configuration, Docker, Helm, health, metrics and operations |
| AWS discovery | IAM setup, cross-account roles, scanning and import |
| HTTP API | The v1 API contract |
| Development | Local setup without Docker, tests and smoke tests |
| Design system | The console's visual language and components |
crates/vda-guard SQL safety engine (pure, no I/O)
crates/vda-connectors Guarded execution against PostgreSQL and MySQL
crates/vda-discovery Cloud discovery providers (AWS RDS/Aurora)
crates/vda-server HTTP API, auth, policies, approvals, audit (binary)
web/ React + TypeScript console, embedded in the binary
deploy/ Helm chart, IAM policies, demo seed data
scripts/ Local development and smoke-test scripts
visp-db-access is pre-1.0. The API and storage schema may still change between releases. Supported targets are PostgreSQL and MySQL (including MariaDB and their managed variants such as RDS, Aurora, Cloud SQL and Azure Database).
Roadmap: RDS IAM authentication; GCP Cloud SQL and Azure discovery; OIDC/SAML SSO and SCIM; group grants; just-in-time access requests; saved queries; distributed query cancellation; durable audit delivery and SIEM export; classification-driven masking; MongoDB and SQL Server engines; SSH/bastion tunnels.
Contributions are welcome; see CONTRIBUTING.md. Please report vulnerabilities privately as described in SECURITY.md.
Licensed under the Apache License, Version 2.0. See NOTICE for attributions.