{"html_url": "https://github.com/simonw/datasette/issues/188#issuecomment-738905376", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/188", "id": 738905376, "node_id": "MDEyOklzc3VlQ29tbWVudDczODkwNTM3Ng==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2020-12-04T17:18:34Z", "updated_at": "2020-12-04T17:18:34Z", "author_association": "OWNER", "body": "This is likely to be covered by plugin hooks: #860 for the metadata and after investigating in #1042 it looks like the existing `prepare_jinja2_environment` hook may already be enough to load templates from the database.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 309047460, "label": "Ability to bundle metadata and templates inside the SQLite file"}, "performed_via_github_app": null} {"html_url": "https://github.com/simonw/datasette/issues/188#issuecomment-412291327", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/188", "id": 412291327, "node_id": "MDEyOklzc3VlQ29tbWVudDQxMjI5MTMyNw==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2018-08-11T17:53:17Z", "updated_at": "2018-08-11T17:53:17Z", "author_association": "OWNER", "body": "Potential problem: the existing `metadata.json` format looks like this:\r\n\r\n```\r\n{\r\n \"title\": \"Custom title for your index page\",\r\n \"description\": \"Some description text can go here\",\r\n \"license\": \"ODbL\",\r\n \"license_url\": \"https://opendatacommons.org/licenses/odbl/\",\r\n \"databases\": {\r\n \"database1\": {\r\n \"source\": \"Alternative source\",\r\n \"source_url\": \"http://example.com/\",\r\n \"tables\": {\r\n \"example_table\": {\r\n \"description_html\": \"Custom table description\",\r\n \"license\": \"CC BY 3.0 US\",\r\n \"license_url\": \"https://creativecommons.org/licenses/by/3.0/us/\"\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\n\r\nThis doesn't make sense for metadata that is bundled with a specific database - there's no point in having the `databases` key, instead the content of `database1` in the above example should be at the top level. This also means that if you rename the `*.db` file you won't have to edit its metadata at the same time.\r\n\r\nCalling such an embedded file `metadata.json` when the shape is different could be confusing. Maybe call it `database-metadata.json` instead.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 309047460, "label": "Ability to bundle metadata and templates inside the SQLite file"}, "performed_via_github_app": null} {"html_url": "https://github.com/simonw/datasette/issues/188#issuecomment-398778485", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/188", "id": 398778485, "node_id": "MDEyOklzc3VlQ29tbWVudDM5ODc3ODQ4NQ==", "user": {"value": 12617395, "label": "bsilverm"}, "created_at": "2018-06-20T14:48:39Z", "updated_at": "2018-06-20T14:48:39Z", "author_association": "NONE", "body": "This would be a great feature to have!", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 309047460, "label": "Ability to bundle metadata and templates inside the SQLite file"}, "performed_via_github_app": null} {"html_url": "https://github.com/simonw/datasette/issues/188#issuecomment-376594727", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/188", "id": 376594727, "node_id": "MDEyOklzc3VlQ29tbWVudDM3NjU5NDcyNw==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2018-03-27T16:46:49Z", "updated_at": "2018-05-28T21:34:34Z", "author_association": "OWNER", "body": "One point of complexity: datasette can be used to bundle multiple .db files into a single \"app\".\r\n\r\nI think that's OK. We could require that the `datasette_files` table is present in the first database file passed on the command-line. Or we could even construct a search path and consult multiple versions of the table spread across multiple files.\r\n\r\nThat said... any configuration that corresponds to a specific table should live in the same database file as that table.\r\n\r\nDitto for general metadata: if we have license/source information for a specific table or database that information should be able to live in the same .db file as the data.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 309047460, "label": "Ability to bundle metadata and templates inside the SQLite file"}, "performed_via_github_app": null}