Nostr Web Client

I'm not? I'm literally one of two people working on building CICD pipelines into nostr....

If you use act, it uses the same engine as github pipelines does. This is how it needs to be so there 0 work that has to be done to migrate off github. Also by using act, you get the benefit of being able to use all of the actions in the github market place.

I brought up Gitea as well, which can be self hosted just as easily as this tool you're talking about, it's pipelines work just like github actions and it has additional functionality besides just being able to build apks. I'm not promoting github, bit it is the default, so using tools that make migrating away from them should be the path forward, not requiring additional steos.

Derek Ross 6d ago

okay, then i misunderstood why you were referencing it.

i was told yesterday that Dan Conway's ngit wasn't ready for CI CD yet, so i went this route. maybe in a couple months i change it when it's ready, but im not waiting around for that.

to me it sounds like if you're already aware of these tools then you can setup Android builds already and build your own APKs with those tools. what i built isn't for those people though. this is for people that want to roll their face across a keyboard and get an app.

perhaps this is just a diference of audiences?

Reply to this note

Please Login to reply.

Discussion

AU9913 6d ago

Maybe. The code is already being committed to some repo somewhere right? Where is that? I already have nostr:nprofile1qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3cppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhscs6htm's loom protocol working in budabit (same thing as gitworkshop), I just don't have the ui built for it, which will only take a day or two to get done, but you can integrate to loom directly, you don't need budabit or gitworkshop or whoever as a middle man.

The benefits of doing it that way are that you can use the same pipeline structure for non-apk stuff too. Like if someone wants to publish the app as an nsite, they can use the github action that already exists to do that (on github or not). They could also add whatever other jobs to their app too, for example, if it's a website, they can use the piepliento deploy DNS entries, do stuff on Dev branches, etc.

Arjen 6d ago

nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy08wumn8ghj7mn0wd68yttjv4kxz7fwv3jhyettwfhhxuewd4jsqgplwuxkt5a8vj5utj6s8tsj8e3wcavc45p4mqmw92qs7wrh5azmys9f0hy6 here's an example run of a github workflow (.yaml) over nostr.

https://hive-ci.treegaze.com/run/2e616b4c08cd20fee97cd2f0af35fd151868f12a34774d1e2fa8d4b9389d19f5

Loom: Arbitrary command execution, paid with cashu

HiveCI: Leverages Loom to run GitHub actions

The underlying loom job that HiveCI executes: https://loom.treegaze.com/job/87d676b0c7c31846862bcfa3d841a32d2e0cc3abef05d689f4789e71fc139f71

Since I follow you you have permission to use my runner and should be able to login and hit re-run job. (make sure you load up some testnut.cashu.space nuts)