it's all coming together. 
Discussion
Whaaaat. Thats cool.
Why tho? You can just run it on github or even run a github pipeline locally?
A lot of Shakespeare seems to be doing stuff that lots of other things already do. The secret sauce is supposed to be nostr. Somehow.
Because it needs to be one button click easy for people that don't know what any of the words are that you just said.
Sure... You can use existing tools and standards to do that though? You don't need a self - hosted solution, if that is your audience, your added extra steps that will just make maintenance harder.
This isn't for everyone. It's for those that don't want to use big tech, want to be self sovereign, and aren't technical. You're see when it's all done.
Maybe it would also make sense at some point to translate the Shakespeare UI into different languages.
Ok, I'll defer to you until I see it, but you can self host Gitea and just have the AI build workflows there instead of a single purpose server. Also, we have CICD on nostr...
Ngit doesn't support CICD yet. This works now. And we'd have to have one for GitLab, one for GitHub, and one for ngit. I looked at paid solutions too. This is honestly easier for not only vibe coders to build app and people that want to also host their own build server.
No, we have CICD pipeline running via loom. I have one hard coded in budabit. And you don't need one for gitlab and github and ngit,
This is how you use github actions locally and how we are running CICD stuff on nostr. GitLab already let's you run stuff locally too. Gitea uses act runners as well.
So I don't see why you wouldn't just use act with marketplace actions to make these apks. Kinda creating a vendor lock situation
How is this easier for vibe coders and self hosters? Self hosters already have Gitea. Vibe coders already have github.
why do you keep promoting using github? we should be trying to get away from using centralized services.
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.
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?
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.
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)
act seems really cool, but it doesn't work for shakespeare users. they would need to have a local server or computer to run this. how are they supposed to use this on their phones?
Are you building APKs on peoples phones with this? Because that is an entirely different conversation. The picture says "self-hosted" which I have never heard used to describe an application you're running on your phone.
This is a Shakespeare thing?
I'm curious if it integrates with trymaple.ai? AFAIK, maple doesn't integrate with vscode which is currently a bit of a downer for me.
nostr:nprofile1qqs8msutuusu385l6wpdzf2473d2zlh750yfayfseqwryr6mfazqvmgpy4mhxue69uhkvet9v3ejumn0wd68ytnzv9hxgtm0d4hxjh6lwejkuar4wfjhxqfswaehxw309a5hgcmg0ykkwmmvv3jkuun0vskkvatjvdhkuargdacxsct8w4ejuumrv9exzc3wd9kj7qfpwaehxw309ahx7um5wgkhyetvv9ujuar90pshx6r9v3nk2tnc09az7em0qzz nostr:nprofile1qqsf5jlaagkyhy33qlvcxkluhtyy3l7y65upsf405w5ya0vlms5rmrgpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcprfmhxue69uhhyetvv9ujummjv9hxwetgv96zuanfwqhsgvw2tl
You knew
You know, I know
👀👀👀
A little of zapstore, a little that, a little this... I see a full fledged F-Droid replacement incoming.
🫂💜🔥
You got a link to this code?