Commit graph

13 commits

Author SHA1 Message Date
96f5ddfca6
bail out after 20 unexpected connect failures (takes overnight) 2025-04-04 12:08:10 -07:00
74d9440bec
allow more logging control 2025-04-01 13:46:57 -07:00
aee9b34ec7
add event action to the things the watcher matches 2025-04-01 13:46:31 -07:00
fbdc4bbdf2
skip old events on first run 2025-04-01 13:45:34 -07:00
02c37f086f
authorization, end to end tests, and fix config processing 2025-04-01 12:02:39 -07:00
0b810b0604
fail on auth failures 2025-04-01 09:43:02 -07:00
a6de83b7c5
add arena for main loop allocator 2025-04-01 09:24:29 -07:00
9592d4da42
get tests compiled/passing 2025-04-01 09:16:35 -07:00
db23724e32
add gitignore 2025-04-01 08:46:27 -07:00
02c17c4d71
make it compile 2025-04-01 08:45:20 -07:00
a584d3ed46
add AI generated whatever
I want a cli application written in zig 0.14.0 that continuously polls a syncthing events url (http://localhost:8384/rest/events?events=ItemFinished) by default. Syncthing uses the id in the json output to track the last event, so it will need to handle "since=<id>" in the query string after the first request. For all items returned, it should check all the events to see if they match anything configured by the user (the config file can be json, zon, or yaml format). The configuration must allow specification of the folder and path regular expression. If an event matches one of the configured items, the configuration will specify a system command that will be run synchronously, using stdout and stderr of the process. Tests should be written to verify accuracy of the parsing logic for both configuration and events, and the README must document the application. Also, please create a devfile.yaml for future use.
2025-03-31 16:54:36 -07:00
c2a99972be
initial commit 2025-03-31 15:45:23 -07:00
2a1d86e1df
initial commit 2025-03-31 15:44:19 -07:00