aboutsummaryrefslogtreecommitdiffstats
path: root/build/schema.sql
Commit message (Collapse)AuthorAgeLines
* Update psql schema to match tg19 changestg19_psql_schemaOle Mathias Aa. Heggem2019-10-13-91/+13
|
* Copy current schema.sql to ansible roleLasse Haugen2019-02-13-1/+1
|
* Add basic collector-implementationKristian Lyngstol2019-02-13-4/+109
| | | | | | | | | | | | | | | References #195 This is the first dumb-ass implementation of the collector-api. It actually works fine for write AS IS, but has 0 safties. But I'm thinking the API itself is reasonably stable and ready for testing. I will need to extend it for dhcp-specific stuff, and the plan is to create a secondary table with metadata (hidden from the user) and a few other nice things. Also, indexes. We need indexes. Obviously.
* Update schemaKristian Lyngstol2019-01-03-158/+203
|
* SQL: Nuke more unused relics of the pastKristian Lyngstol2016-11-15-89/+1
|
* Remove switch_temp table relic....Kristian Lyngstol2016-11-15-30/+0
| | | | Hasn't been used since tg15 afaik.
* Start clean switches-tableKristian Lyngstol2016-11-15-5/+1
| | | | Lots of cruft
* Last tweak of schemat:Kristian Lyngstol2016-09-10-1/+1
|
* Schema-updateKristian Lyngstol2016-09-10-0/+1
|
* sql: Bump schema to include multi-dhcpd-supportKristian Lyngstol2016-06-30-2/+3
|
* Remove comments from SQLKristian Lyngstol2016-05-18-69/+0
|
* Add SQL for backlog stuff too (ops)Kristian Lyngstol2016-05-18-0/+43
|
* Add config read-api and use it to detect public accessKristian Lyngstol2016-05-16-1/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | Currently no way to modify the settings except by manual SQL, but it's coming. This allows us to have event-specific configuration in the database. This commit adds js that uses this to detect if the frontend is a public vhost or not. There are currently only three columns provided in addition to ID. publicvhost: The domain name of the publicly accessible version of Gondul. shortname: code name for the vent. e.g dx16, tg17, etc. data: jsonb to contain most other settings as we see fit. Most settings will be stored in 'data' if it's only or mainly used by the frontend. This will allow frontend developers to supply arbitrary configuration options without the need for API or database changes in the future. Fixes #51 References #54 Still need the GUI for it.
* Add schema and start build and test-frameworkKristian Lyngstol2016-04-13-0/+682
DB is looking OK so far in the test.