SimpleCloudNotifier/scnserver
2023-01-16 20:29:49 +01:00
..
.idea create migration script for old data 2023-01-15 06:30:30 +01:00
api Tests[TestSendCompatMessageByQuery, TestSendCompatMessageByFormData] 2023-01-16 20:29:49 +01:00
cmd create migration script for old data 2023-01-15 06:30:30 +01:00
db Tests[TestSendCompatMessageByQuery, TestSendCompatMessageByFormData] 2023-01-16 20:29:49 +01:00
google move server/* to scnserver/* 2022-12-21 12:35:56 +01:00
jobs Move to string-ids for all entities (compat translation for existing data) 2023-01-14 00:48:51 +01:00
logic create migration script for old data 2023-01-15 06:30:30 +01:00
models create migration script for old data 2023-01-15 06:30:30 +01:00
push Move to string-ids for all entities (compat translation for existing data) 2023-01-14 00:48:51 +01:00
swagger create compat-id for messages && TestCreateCompatUser 2023-01-16 18:53:22 +01:00
test Tests[TestSendCompatMessageByQuery, TestSendCompatMessageByFormData] 2023-01-16 20:29:49 +01:00
website Tests[TestSendCompatMessageByQuery, TestSendCompatMessageByFormData] 2023-01-16 20:29:49 +01:00
.gitignore create migration script for old data 2023-01-15 06:30:30 +01:00
config.go create migration script for old data 2023-01-15 06:30:30 +01:00
Dockerfile move server/* to scnserver/* 2022-12-21 12:35:56 +01:00
go.mod create migration script for old data 2023-01-15 06:30:30 +01:00
go.sum create migration script for old data 2023-01-15 06:30:30 +01:00
init.go cherry-pick caller logprint fix from psycho-backend 2023-01-13 17:51:55 +01:00
Makefile create migration script for old data 2023-01-15 06:30:30 +01:00
README.md create migration script for old data 2023-01-15 06:30:30 +01:00
util.go create migration script for old data 2023-01-15 06:30:30 +01:00

TODO

BEFORE RELEASE

  • finish tests (!)

  • migration script for existing data apply local deletion in (my) app delete excessive dockerwatch messages (directly in db?)

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

  • convert existing user-ids on compat /send endpoint

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

  • endpoint to list all servernames of user (distinct select)

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

  • (?) add querylog (similar to requestlog/errorlog) - only for main-db

LATER