2022-11-19 17:09:23 +01:00
|
|
|
|
|
|
|
|
|
2022-11-30 10:35:05 +01:00
|
|
|
TODO
|
|
|
|
|
========
|
2022-11-19 17:09:23 +01:00
|
|
|
|
2022-11-30 10:35:05 +01:00
|
|
|
-------------------------------------------------------------------------------------------------------------------------------
|
2022-11-21 22:52:44 +01:00
|
|
|
|
2022-11-21 18:46:55 +01:00
|
|
|
- migration script for existing data
|
2022-11-19 17:09:23 +01:00
|
|
|
|
2022-11-21 22:52:44 +01:00
|
|
|
- app-store link in HTML
|
2022-11-21 18:46:55 +01:00
|
|
|
|
2022-11-30 10:35:05 +01:00
|
|
|
- route to re-check all pro-token (for me)
|
2022-11-25 22:42:21 +01:00
|
|
|
|
2022-11-30 10:35:05 +01:00
|
|
|
- tests (!)
|
2022-11-23 19:32:23 +01:00
|
|
|
|
2022-11-20 20:34:18 +01:00
|
|
|
- deploy
|
2022-11-29 11:07:15 +01:00
|
|
|
|
2022-12-20 09:22:18 +01:00
|
|
|
- diff my currently used scnsend script vs the one in the docs here
|
|
|
|
|
|
2022-12-22 12:43:40 +01:00
|
|
|
- Pagination for ListChannels / ListSubscriptions / ListClients / ListChannelSubscriptions / ListUserSubscriptions
|
|
|
|
|
|
2022-12-22 17:29:59 +01:00
|
|
|
- cannot open sqlite in dbbrowsr (cannot parse schema?)
|
2023-01-13 12:43:20 +01:00
|
|
|
-> https://github.com/sqlitebrowser/sqlitebrowser/issues/292 -> https://github.com/sqlitebrowser/sqlitebrowser/issues/29266
|
2022-12-22 17:29:59 +01:00
|
|
|
|
2022-12-23 20:27:21 +01:00
|
|
|
- (?) use str-ids (also prevents wrong-joins) -> see psycho
|
2023-01-13 12:43:20 +01:00
|
|
|
-> how does it work with existing data? (do i care, there are only 2 active users... (are there?))
|
2022-12-23 20:27:21 +01:00
|
|
|
|
|
|
|
|
- error logging as goroutine, get sall errors via channel,
|
|
|
|
|
(channel buffered - nonblocking send, second channel that gets a message when sender failed )
|
|
|
|
|
(then all errors end up in _second_ sqlite table)
|
|
|
|
|
due to message channel etc everything is non blocking and cant fail in main
|
|
|
|
|
|
2023-01-06 00:39:21 +01:00
|
|
|
- request logging (log all requests with body response, exitcode, headers, uri, route, userid, ..., tx-retries, etc), (trim body/response if too big?)
|
|
|
|
|
|
|
|
|
|
- jobs to clear requests-db and logs-db after to only keep X entries...
|
|
|
|
|
|
|
|
|
|
-> logs and request-logging into their own sqlite files (sqlite-files are prepped)
|
|
|
|
|
|
2023-01-13 12:43:20 +01:00
|
|
|
- /send endpoint should be compatible with the [ webhook ] notifier of uptime-kuma
|
|
|
|
|
(or add another /kuma endpoint)
|
|
|
|
|
-> https://webhook.site/
|
|
|
|
|
|
2022-11-30 10:35:05 +01:00
|
|
|
-------------------------------------------------------------------------------------------------------------------------------
|
|
|
|
|
|
2023-01-13 12:43:20 +01:00
|
|
|
- in my script: use `srvname` for sendername
|
2022-11-29 11:07:15 +01:00
|
|
|
|
2022-11-30 10:35:05 +01:00
|
|
|
-------------------------------------------------------------------------------------------------------------------------------
|
|
|
|
|
|
2022-12-22 11:22:36 +01:00
|
|
|
- (?) default-priority for channels
|
|
|
|
|
|
2022-11-30 10:35:05 +01:00
|
|
|
- (?) ack/read deliveries && return ack-count (? or not, how to query?)
|
|
|
|
|
|
2022-12-14 18:38:30 +01:00
|
|
|
- (?) "login" on website and list/search/filter messages
|
2022-11-30 10:35:05 +01:00
|
|
|
|
2023-01-13 12:43:20 +01:00
|
|
|
- (?) make channels deleteable (soft-delete) (what do with messages in channel?)
|
|
|
|
|
|
|
|
|
|
- (?) desktop client for notifications
|
|
|
|
|
|
