Automatically publish binaries to nextcloud

Updated the releases directory to use a specific account for releases

.tangled/workflows/build.yml

@@ -0,0 +1,26 @@
+when:
+  - event: ["push", "pull_request", "manual"]
+    branch: ["dev", "master", "test*"]
+    tag: ["v*"]
+
+engine: "nixery"
+
+dependencies:
+  nixpkgs:
+    - rclone
+  git+https://github.com/mitchellh/zig-overlay:
+    - master
+
+steps:
+  - name: "Build"
+    command: "zig build --release=fast -Dcpu=baseline"
+  - name: "Publish"
+    command: |
+      rclone sync ./zig-out \
+        --webdav-url "$RELEASE_NEXTCLOUD_HOST/remote.php/dav/files/$RELEASE_NEXTCLOUD_USER/" \
+        --webdav-user "$RELEASE_NEXTCLOUD_USER" \
+        --webdav-pass "$RELEASE_NEXTCLOUD_PASS" \
+        --webdav-vendor nextcloud \
+        :webdav:"zaprus/zaprus-$TANGLED_REF_NAME" \
+        -q
+

README.md

@@ -3,4 +3,4 @@
 This is an implementation of the [Saprus protocol](https://gitlab.com/c2-games/red-team/saprus) in Zig.
 It is useful for developing clients either in Zig, or in any other language using the C bindings.
 
-Binary releases can be downloaded [here](https://cloud.zambito.xyz/s/cNaLeDz38W5ZcZs).
+Binary releases can be downloaded [here](https://cloud.zambito.xyz/s/7jJPTm68Zp3mN8F).