abs_cd VS ht

Get a CI to check if pkg build in clean environments. So many users will falsely report broken packages while they simply ran makepkg in their arch installation & the build system pulls crap from it into the build process & it fails despite your pkg being fine. It's a shame every AUR helper except aurutils still doesn't support building in clean chroots, but you can't change that. I build https://github.com/bionade24/abs_cd for that, which end the end served a custom repo easing the installation for users, too. There are plenty alternatives to my SW out there, too.

You can find the CD status on https://abs-cd.oscloud.info/

This commit should also be a good example on how to configure crond to work well with logging in an Arch container.

https://github.com/bionade24/abs_cd

A CI/CD with webinterface for Archlinux packages which optional AUR push support if builds succeed. It's based on Django and works with Docker/Podman. I originally made it for my own AUR packages (> 300), I needed accessible build logs if I want to collab, which the common builders didn't provide. I made the project public and it's crazy for me as an open source beginner to see how many people like this. The basic features are complete, but things like multiarch are getting add soon.

It now has podman compatibility as as a PR: https://github.com/bionade24/abs_cd/pull/8

It now should have podman compatibility, would be nice if you test it: https://github.com/bionade24/abs_cd/pull/8

If it really takes that long (and you maybe have more than one device or your friends use the same packages) and you can't find a user already packaging it in their private repo you could host an own repo in you local network. I created a CI/CD software for Arch packages which makes this easier: https://github.com/bionade24/abs_cd

No need to use curl, make HTTP requests great again with https://github.com/ducaale/xh

Except when you actually enjoy things being fast. For example, HTTPie easily adds 0.5-1s delay to every request because it's written in Python, especially on the first invocation. xh (https://github.com/ducaale/xh), on the other hand, starts immediately because it's written in Rust. I very much like this trend.

HTTPie is great and was a big improvement for me over cURL.

However, I ended up switching to xh[1] as it's significantly faster and I prefer its output.

https://github.com/ducaale/xh

No, but unless portability is a concern or you're massively familiar with curl, you might want to consider xh. It's much more intuitive.

https://github.com/ducaale/xh

xh

wget on the other hand, automatically converts the ñ to UTF-8 hex and resolves the link perfectly.

I've searched the curl manpage and couldn't find a way to solve this. Please help.

I'm having to use `xh --curl` [1] to "fix" the links before I pass them to curl.

[1] https://github.com/ducaale/xh

Very nice, you should add xh to the User-Agents though.

While not a rewrite - one recent tool for making http requests which i quite enjoy is:

https://github.com/ducaale/xh

It's basically python httpie rewritten in rust. my only gripe is that i keep forgetting that it exists - and that "xh" is for http and "xhs" is for https.

So i frequently end up with curl anyway:)