# Create DB Table Historian via scripting **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [November 2, 2025, 5:24pm UTC](https://forum.inductiveautomation.com/t/create-db-table-historian-via-scripting/111876 "2025-11-02T17:24:48Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [November 3, 2025, 5:19pm UTC](https://forum.inductiveautomation.com/t/create-db-table-historian-via-scripting/111876/4 "2025-11-03T17:19:26Z")
That's the plan. Everything that you can do via CRUD in the REST API will be possible via `system.config` - some ergonomics will obviously be different but the final capability should be exactly equivalent. Worth noting also that there may be better options for the "manually create all the things each time" story - e.g. the `external` resource collection in 8.3: > [@Building Custom Ignition Gateway Docker Images](https://forum.inductiveautomation.com/t/building-custom-ignition-gateway-docker-images/111899/2): > > Don't mount into /data/, that's too broad. If you need to load 'gateway config', then mount the things you care about from /data/config/resources/core/ (on your development system) into the container at the /data/config/resources/external/ directory. The external directory is automatically scanned in on gateway startup and treated as an immutable set of resources that the gateway will not ever attempt to make changes to. Some more context: The project inheritance situation is different, but … --- _[View the full topic](https://forum.inductiveautomation.com/t/create-db-table-historian-via-scripting/111876)._