131b792cea
add mention of docker images in README
Generic zig build / build (push) Successful in 1m25s
2025-04-13 14:46:06 -07:00
f6e9b1004b
update zig-action-cache to latest
Generic zig build / build (push) Successful in 13m26s
2025-04-13 14:30:19 -07:00
da994fe9e6
add names for all steps
2025-04-13 14:29:27 -07:00
958ce3af46
what a difference a trailing slash makes
Generic zig build / build (push) Has been cancelled
2025-04-13 14:20:31 -07:00
5bbc7e5e57
add entrypoint for dockerfile
Generic zig build / build (push) Successful in 13m26s
2025-04-13 14:03:03 -07:00
15aac15573
enable latest tag
Generic zig build / build (push) Successful in 54s
2025-04-12 23:00:29 -07:00
a2a7130adc
fix s390x and dockerfile syntax issues
Generic zig build / build (push) Successful in 13m36s
2025-04-12 16:31:20 -07:00
0def6c7932
fix typo in docker push
Generic zig build / build (push) Failing after 12m48s
2025-04-12 15:33:53 -07:00
d0954e7f02
change line endings (and url for mlugg/setup-zig)
Generic zig build / build (push) Failing after 14m17s
2025-04-12 15:10:30 -07:00
171dd2e96e
update urls for github
Generic zig build / build (push) Failing after 7s
2025-04-12 15:08:24 -07:00
8dc9ec38fd
forgejo default url is mucking with this. Change over for now
2025-04-12 15:07:14 -07:00
d7192aa720
switch to mlugg/setup-zig
Generic zig build / build (push) Failing after 6s
2025-04-12 14:55:45 -07:00
ba251b4b80
docker multi-platform build support and ci
Generic zig build / build (push) Failing after 8s
2025-04-12 14:47:27 -07:00
45eae9800f
change publish source
Generic zig build / build (push) Successful in 1m39s
2025-04-10 18:19:16 -07:00
85bc4e1286
skip tests that fail in ReleaseSafe
Generic zig build / build (push) Failing after 1m39s
2025-04-10 18:11:55 -07:00
fa05e06236
fix up tests
Generic zig build / build (push) Failing after 48s
2025-04-10 11:19:53 -07:00
d989a48501
add release mode tests and package/publish
Generic zig build / build (push) Failing after 31s
2025-04-10 10:41:32 -07:00
776eb870a9
add ci from template
2025-04-10 09:40:40 -07:00
2fd37ab057
add small StackFallbackAllocator to handle most processing
2025-04-09 15:08:23 -07:00
56cd0714ac
fix fd leak
2025-04-08 09:49:08 -07:00
a8f57197a7
better stdout logging
2025-04-08 09:49:00 -07:00
b491449295
better dump action
2025-04-07 12:28:35 -07:00
dcf157f4d6
add new event_type, action, and dump variables
2025-04-07 12:17:01 -07:00
ea0f079473
reformat
2025-04-07 12:16:42 -07:00
d9398c0843
fix path discrepency between event types
2025-04-07 12:16:25 -07:00
1e2691683a
pass full event into watcher match
2025-04-07 12:15:56 -07:00
f04e851a66
add event type filter capability to watcher
2025-04-07 12:13:57 -07:00
771d7d7b4c
add connection pool to hopefully eliminate unexpected connection failures
2025-04-04 12:09:21 -07:00
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