xavi/upload-artifact, branch masterCommand-line application to upload files to a slcl instance and share them.
https://gitea.privatedns.org/xavi/upload-artifact/atom?h=master2026-03-06T04:36:18+00:00Fix error checking inside upload_all()2026-03-06T04:36:18+00:00Xavier Del Campo Romeroxavi92@disroot.org2026-03-06T04:36:18+00:00urn:sha1:ee80de959be80e382952fec36e11674fff6539d0
Because of historical reason, set -e is ignored inside function bodies
[1], which caused the script to attempt to share a file even if the
upload had failed.
[1]: https://lists.gnu.org/archive/html/bug-bash/2012-12/msg00094.html
Replace --fail-with-body with -f2025-04-17T05:52:55+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-04-17T05:52:55+00:00urn:sha1:bd32b8f01b946a8856f2e1ab907122842447e11a
The former might not be available on older versions of cURL, such as
that distributed by Ubuntu focal. Also, upload-artifact is not
interested in the HTTP body returned on 4xx errors, so the latter is
more appropriate.
upload-artifact: Set default directory on getdir2025-01-26T07:52:40+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-26T07:52:40+00:00urn:sha1:60f13a8717082626fabefa82417b050d6339a177
Otherwise, uploads without the `-d` flag are broken because the first
file is considered the directory to upload to.
upload-artifact: Add missing ;;2025-01-26T07:52:21+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-26T07:52:21+00:00urn:sha1:a85228858749d33f7d0d2356d85dac68bfdf4521Support uploading artifacts to a directory2025-01-13T16:02:44+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-13T16:02:44+00:00urn:sha1:2ddaeadd4f11551fd7a711153e2067bad7600a01
So far, the root directory (i.e., /) was assumed as the directory to
upload artifacts to. This might be too limiting for some users.
Add README.md2025-01-12T00:54:18+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-12T00:52:32+00:00urn:sha1:e60e313f81326b5c2fd28d1f55ac4311a3a3ce16upload-artifact: Force curl(1) not to send "Expect" header2025-01-12T00:53:16+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-08T22:56:26+00:00urn:sha1:b51e1c0e0f1dc42620765dd672360998a3238e1f
Under some circumstances, curl(1) sends 100-continue to the HTTP server.
[1] While this is handled correctly by slcl, when used together with
Apache as a reverse proxy, for some unknown reason the Content-Length is
not sent to slcl by Apache, and therefore returns a 502 Proxy Error.
Setting the proxy-sendcl environment variable [2] to Apache did not help,
either.
[1]: https://gms.tf/when-curl-sends-100-continue.html
[2]: https://httpd.apache.org/docs/current/mod/mod_proxy.html#request-bodies
upload-artifact: Replace USER with USERNAME2025-01-12T00:53:16+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-08T21:36:22+00:00urn:sha1:a481304b911b3ceea91bf11d6ca4f072fa6e5fa2
USER is an environment variable that might be already defined by the
shell.
Introduce upload-artifact2025-01-12T00:53:11+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2025-01-08T21:16:07+00:00urn:sha1:86411fc51d4efb6508a26d66246ec795d568f4f8
As its name suggests, this simple shell script allows to upload one or
more artifacts to a slcl instance.