fix(supabase): db:trial database logs no statement from its first start
The image's init (migrate.sh) sent the supabase_admin password as SQL text while its postgresql.conf logged DDL, so the password reached the container log. The server now starts with -c log_statement=none, which the entrypoint also hands to the init server; a harness check pins it, and DEPLOY.md makes the post-init log scan a production prerequisite.
This commit is contained in:
1 parent
c6c984b954
commit
5f63d2229c
4 files changed
+15
-2
No files matched your search
@@ -46,6 +46,13 @@ Security prerequisites before deploying anything built from `develop`:
|
||||
- the worker's service key out of `.env`, its exposure to the `docker` group
|
||||
settled (RR-4);
|
||||
- images built off the VPS and pulled by digest, base images pinned (RR-6);
|
||||
- a self-hosted Supabase database on the `supabase/postgres` image starts with
|
||||
`-c log_statement=none` on its server command line from its very first
|
||||
start (the image's init sends role passwords as SQL text while its
|
||||
`postgresql.conf` logs DDL; the entrypoint passes the flag to the init
|
||||
server), and right after init its container log (and log files, if any) is
|
||||
scanned for the password, counts only, before anything else
|
||||
(`docs/development/SUPABASE.md` §5.2);
|
||||
- the RLS and API items of RR-3 and RR-4 and the dependency advisories of
|
||||
RR-1 treated or qualified.
|
||||
|
||||
|
||||
Reference in new issue
Block a user