cargo-binstall
act
cargo-binstall | act | |
---|---|---|
24 | 146 | |
1,304 | 50,324 | |
4.8% | 1.8% | |
9.5 | 9.2 | |
1 day ago | 5 days ago | |
Rust | Go | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-binstall
-
Cargo Binstall 1.0.0 release
Unfortunately not really usable in production (for me) until https://github.com/cargo-bins/cargo-binstall/issues/1 is fixed :( Really much looking forward to it though, as I think it's a great addition to the Rust ecosystem!
-
Oxidise your Infrastructure using Shuttle.rs
Oh looks like cargo-binstall is currently broken (https://github.com/cargo-bins/cargo-binstall/issues/1094)
-
Ludusavi can now back up your game saves to the cloud and detect Lutris saves
Unfortunately, I ended up running into an issue with the zip support, but I'll come back to it once this is fixed: https://github.com/cargo-bins/cargo-binstall/issues/1080
-
Strange lifetime error: Requires to be `'static`
I've encountered a strange lifetime error when developing new features in cargo-binstall:
-
AMDGPU_TOP - tool to show AMDGPU usage
Once you feel like releasing it, could you please add binstall support?
-
[rcargo] quick tool for faster crate building on remote workstations
I think in a similar vein there is cargo-binstall that is a cargo install alternative that attempts to use pre-built binary artifacts when possible
-
Faster Apple Builds with the lld Linker
I hope ld64 and lld add supports for plugin-opt I'm trying to enable cross-lang-lto on MacOS but failed due to -plugin-opt not supported.
-
Install a CLI in a project (not globally)
You can use cargo-binstall --install-path to install binaries to custom locations.
-
Release engineering is exhausting so here's cargo-dist
If you happen to install a lot of things with cargo, check out cargo-binstall: https://github.com/cargo-bins/cargo-binstall
It'll fetch the binary release from the repo so you don't have to compile it yourself.
-
Thoughts about updating a rust cli via a sub command for improved dev experience
I'd recommend to use cargo-binstall, which can download pre-built artifacts from github release.
act
-
Create a Custom GitHub Action in Rust
To speed up your development cycle, install and use the act tool to test-run your action directly in your development environment. This tool lets you invoke a GitHub workflow right on your local machine and will save you the round-trips of pushing each change to GitHub to see if it works.
-
How to debug GitHub actions. Real-world example
When it comes to the alternatives to tmate, there is another great debugging tool that you could check out. It is called act and it allows you to run GitHub Actions code on your local machine making debugging even easier. It has its own limitations and some learning curve but overall it is another tool you should use if you can’t fix the CI bugs by connecting directly into the running action with the tmate.
-
Using my new Raspberry Pi to run an existing GitHub Action
Link: https://github.com/nektos/act
-
Show HN: Open-source x64 and Arm GitHub runners. Reduces GitHub Actions bill 10x
Could you upload your build of GitHub's runner image to Docker Hub?
This would be quite useful for users of other GitHub Actions clones like act [0].
[0]: https://github.com/nektos/act
-
Git commit messages are useless
> These kinds of commit messages are typically an indicator of a broken process where somebody needs to commit to see something happen, like a deployment or build process, and aren't able to assert that stuff works locally.
This is one of my biggest pet peeves with services like github actions. Something running locally like "act" [1] isn't sufficient because it doesn't have everything github has and is extra friction anyway to get everyone to use it for testing.
[1] https://github.com/nektos/act
-
Essential Command Line Tools for Developers
View on GitHub
-
What’s with DevOps engineers using `make` of all things?
If you use Github actions, act is incredibly useful. It can be used to test your GH actions, but also serves as an interface for running tasks locally.
-
Streamlining CI/CD Pipelines with Code: A Developer's Guide
That's something that often is difficult or basically impossible. Except for maybe GitHub actions through Act (https://github.com/nektos/act). I'd still lean to something in the yaml sphere if it eventually would be used in deployment pipelines and such. For example a solution incorporating ansible.
It also seems to me that the argument you make is mostly focused on the building step? Earthly certainly seems focused on that aspect.
-
GitHub Actions Are a Problem
I feel I'm being trolled, but I'll bite and accept the resulting downvotes
I don't think treating every mention of act as an opportunity for airing of personal grievances is helpful in a discussion when there's already ample reports of people's concrete issues with it, had one looked at the 800 issues in its repo https://github.com/nektos/act/issues?q=is%3Aissue or the 239 from gitea's for https://gitea.com/gitea/act_runner/issues or whatever is going on with Forgejo's fork https://code.forgejo.org/forgejo/act .
But, as for me specifically, there are two and a half answers: I wanted to run VSCodium's build locally, which act for sure puked about. Then, while trying to troubleshoot that, I thought I'd try something simpler and have it run the lint job from act's own repo <https://github.com/nektos/act/blob/1252e551b8672b1e16dc8835d...> to rule out "you're holding it wrong" type junk. It died with
[checks/lint] Failure - Main actions/setup-go@v3
-
How Steve Jobs Saved Apple with the Online Apple Store
https://twitter.com/mitsuhiko/status/1720410479141487099 :
> GitHub Actions currently charges $0.16 per minute* for the macOS M1 Runners. That comes out to $84,096 for 1 machine year*
GitHub Runner is written in Go; it fetches tasks from GitHub Actions and posts the results back to the Pull Request that spawned the build.
nektos/act is how Gitea Actions builds GitHub Actions workflow YAML build definition documents. https://github.com/nektos/act
https://twitter.com/MatthewCroughan/status/17200423527675700... :
> This is the macOS Ventura installer running in 30 VMs, in 30 #nix derivations at once. It gets the installer from Apple, automates the installation using Tesseract OCR and TCL Expect scripts. This is to test the repeatability. A single function call `makeDarwinImage`.
With a Multi-Stage Dockerfile/Containerfild, you can have a dev environment like xcode or gcc+make in the first stage that builds the package, and then the second stage the package is installed and tested, and then the package is signed and published to a package repo / app store / OCI container image repository.
SLSA now specifies builders for signing things correctly in CI builds with keys in RAM on the build workers.
"Build your own SLSA 3+ provenance builder on GitHub Actions" https://slsa.dev/blog/2023/08/bring-your-own-builder-github
What are some alternatives?
pwninit - pwninit - automate starting binary exploit challenges
reverse-rdp-windows-github-actions - Reverse Remote Desktop into Windows on GitHub Actions for Debugging and/or Job Introspection [GET https://api.github.com/repos/nelsonjchen/reverse-rdp-windows-github-actions: 403 - Repository access blocked]
cargo-quickinstall - pre-compiled binary packages for `cargo install` [Moved to: https://github.com/cargo-bins/cargo-quickinstall]
cache - Cache dependencies and build outputs in GitHub Actions
ez_term - Terminal UI framework based on templates and focused on simplicity.
dagger - Application Delivery as Code that Runs Anywhere
nue - I/O and binary data encoding for Rust
earthly - Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
docker-cargo-binstall
action-tmate - Debug your GitHub Actions via SSH by using tmate to get access to the runner system itself.
amdgpu_top - Tool to display AMDGPU usage
LSPatch - LSPatch: A non-root Xposed framework extending from LSPosed