id,node_id,number,state,locked,title,user,body,created_at,updated_at,closed_at,merged_at,merge_commit_sha,assignee,milestone,draft,head,base,author_association,repo,url,merged_by,auto_merge 1504915653,PR_kwDOBm6k_c5ZszDF,2174,open,0,Use $DATASETTE_INTERNAL in absence of --internal,15178711,"#refs 2157, specifically [this comment](https://github.com/simonw/datasette/issues/2157#issuecomment-1700291967) Passing in `--internal my_internal.db` over and over again can get repetitive. This PR adds a new configurable env variable `DATASETTE_INTERNAL_DB_PATH`. If it's defined, then it takes place as the path to the internal database. Users can still overwrite this behavior by passing in their own `--internal internal.db` flag. In draft mode for now, needs tests and documentation. Side note: Maybe we can have a sections in the docs that lists all the ""configuration environment variables"" that Datasette respects? I did a quick grep and found: - `DATASETTE_LOAD_PLUGINS` - `DATASETTE_SECRETS` ---- :books: Documentation preview :books:: https://datasette--2174.org.readthedocs.build/en/2174/ ",2023-09-06T16:07:15Z,2023-09-08T00:46:13Z,,,0fc2896ffc5b49adba967a3d0ab8ac9ca119ba0e,,,0,d75b51950f6836d6e5a58accb48b1d7687dbdd1c,05707aa16b5c6c39fbe48b3176b85a8ffe493938,CONTRIBUTOR,107914493,https://github.com/simonw/datasette/pull/2174,,