SimpleCloudNotifier/scnserver
2023-01-13 17:51:55 +01:00
..
.idea migrate to multiple sqlite db files ( primary + requests + logs ) 2023-01-06 00:39:21 +01:00
api requests-log db 2023-01-13 17:17:17 +01:00
cmd/scnserver requests-log db 2023-01-13 17:17:17 +01:00
db requests-log db 2023-01-13 17:17:17 +01:00
google move server/* to scnserver/* 2022-12-21 12:35:56 +01:00
jobs requests-log db 2023-01-13 17:17:17 +01:00
logic requests-log db 2023-01-13 17:17:17 +01:00
models requests-log db 2023-01-13 17:17:17 +01:00
push move server/* to scnserver/* 2022-12-21 12:35:56 +01:00
swagger Added freely editable description_name field to channel 2023-01-13 12:43:20 +01:00
test requests-log db 2023-01-13 17:17:17 +01:00
website move server/* to scnserver/* 2022-12-21 12:35:56 +01:00
.gitignore move server/* to scnserver/* 2022-12-21 12:35:56 +01:00
config.go requests-log db 2023-01-13 17:17:17 +01:00
Dockerfile move server/* to scnserver/* 2022-12-21 12:35:56 +01:00
go.mod requests-log db 2023-01-13 17:17:17 +01:00
go.sum requests-log db 2023-01-13 17:17:17 +01:00
init.go cherry-pick caller logprint fix from psycho-backend 2023-01-13 17:51:55 +01:00
Makefile Added a SQL-Preprocessor - this way we can unmarshal recursive structures (LEFT JOIN etc) 2022-12-21 18:14:13 +01:00
README.md cherry-pick caller logprint fix from psycho-backend 2023-01-13 17:51:55 +01:00
util.go move server/* to scnserver/* 2022-12-21 12:35:56 +01:00

TODO

BEFORE RELEASE

  • finish tests (!)

  • migration script for existing data

  • app-store link in HTML

  • route to re-check all pro-token (for me)

  • deploy

  • diff my currently used scnsend script vs the one in the docs here

  • (?) use str-ids (hide counts and prevents wrong-joins) -> see psycho -> ensre that all queries that return multiple are properly ordered -> how does it work with existing data? -> do i care, there are only 2 active users... (are there?)

  • error logging as goroutine, gets all 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

  • => implement proper error logging in goext, kinda combines zerolog and wrapped-errors copy basic code from bringman, but remove all bm specific stuff and make it abstract Register(ErrType) methods, errtypes then as structs log.xxx package with same interface as zerolog

  • 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)

  • /send endpoint should be compatible with the [ webhook ] notifier of uptime-kuma (or add another /kuma endpoint) -> https://webhook.site/

PERSONAL

  • in my script: use srvname for sendername

UNSURE

  • (?) default-priority for channels

  • (?) ack/read deliveries && return ack-count (? or not, how to query?)

  • (?) "login" on website and list/search/filter messages

  • (?) make channels deleteable (soft-delete) (what do with messages in channel?)

  • (?) desktop client for notifications

LATER