Open
Conversation
bandle
reviewed
Feb 26, 2026
Comment on lines
+135
to
+136
| CedarDB supports auto-initializing a new database with SQL and shell scripts. Additionally, the docker image accepts `xz`, `gzip`, or `zstd` compressed SQL files. | ||
| Files in `/docker-entrypoint-initdb.d/` are executed or sourced during container setup. Supported file extensions are `.sh`, `.sql`, `.sql.gz`, `sql.xz` and `sql.zst`. |
Contributor
There was a problem hiding this comment.
We might drop zstd in the near future.
Suggested change
| CedarDB supports auto-initializing a new database with SQL and shell scripts. Additionally, the docker image accepts `xz`, `gzip`, or `zstd` compressed SQL files. | |
| Files in `/docker-entrypoint-initdb.d/` are executed or sourced during container setup. Supported file extensions are `.sh`, `.sql`, `.sql.gz`, `sql.xz` and `sql.zst`. | |
| CedarDB supports auto-initializing a new database with SQL and shell scripts. Additionally, the docker image accepts `xz` or `gzip` compressed SQL files. | |
| Files in `/docker-entrypoint-initdb.d/` are executed or sourced during container setup. Supported file extensions are `.sh`, `.sql`, `.sql.gz`, and `sql.xz`. |
bandle
reviewed
Feb 26, 2026
Comment on lines
96
to
118
| #### Domain socket authentication | ||
|
|
||
| To avoid passing credentials in the shell (e.g., because you don't want it to appear in your history), you can run CedarDB in domain socket-only mode: | ||
| To avoid passing credentials in the shell (e.g., because you don't want it to appear in your history), you can run CedarDB in domain socket-only mode: | ||
|
|
||
| ```shell | ||
| docker run --rm -p 5432:5432 \ | ||
| -e CEDAR_DOMAIN_SOCKET_ONLY=yes \ | ||
| --name cedardb \ | ||
| cedardb/cedardb | ||
| ``` | ||
|
|
||
| Then connect from the same host using the domain socket: | ||
|
|
||
| ```shell | ||
| docker exec -it cedardb psql -U postgres | ||
| ``` | ||
|
|
||
| Once connected, you can [manually create users and databases](/docs/references/sqlreference/statements/createrole): | ||
|
|
||
| ```sql | ||
| create user {{username}} superuser with password '1234'; | ||
| create database {{username}}; | ||
| ``` |
Contributor
There was a problem hiding this comment.
You can also drop this part. Alternatively we can now use the init files to set a password.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rephrased the preload data section. I added an .sh file that uses the new process_sql function. The example works now without building a new image, but by volume mounting the files.