#forgejoactions — Public Fediverse posts

RE: https://social.treehouse.systems/@whitequark/116454915873481567

Anyone publishing a Quarto blog with Codeberg Pages? I'm new to this automation stuff, and can't decide between WebHooks, Forgejo Actions, and WoodPecker CI. If I use actions or WoodPecker, it would be just for "quarto render"; any R code output is frozen and will be run on my own computer. I have a custom domain.

#QuartoPub #CodebergPages #GitPages #ForgejoActions #WoodPeckerCI

Anyone know of a guide on how to migrate a Build Awesome (11ty) site to Forgejo from GitHub? I somehow got stuck on the SSH auth setup last I tried 😭 I may just need to try again with fresh eyes.

I've been deploying to Neocities with GitHub Actions thanks to @sophie's great guide. I'm sure Forgejo actions will also be a sticking point so any tips here would be awesome. https://localghost.dev/blog/how-i-deploy-my-eleventy-site-to-neocities/

#Neocities #BuildAwesome #11ty #Forgejo #ForgejoActions

It seems that whenever I look more closely at what #github does, it blows my mind. I had no idea that the actions/checkout which everyone seems to be using to basically run "git clone" is 38k LOC of pure node.js madness.
How about we use 9 lines of shell instead?

👋 @adyxax

https://code.vinyl-cache.org/forgejo/sane-checkout

#forgejo #forgejoActions

Ach, so ein tolles Gefühl, habe nach langer Zeit mal wieder die VM mit dem Forgejo Runer hochgefahren, ein neuen git Tag der aktuellen caddy Version gepusht, schon läuft die Kiste los und baut einen caddy Conatiner mit dem Hetzner DNS Provide Modul. 💓
Nach 3-4 Minuten habe ich also ein neues Image im Codeberg Image Repository =)

#forgejo #forgejoActions #Codeberg #selfhost #Proxmox

After read the #forgejo documentation I build my first #forgejoActions
I like that the forgejo actios are similar to the github action.
https://codeberg.org/codeDude/romodoro-socket/pulls/5/files

My first #ForgejoActions running on #codeberg

Note: I'm using the images that codeberg offer

#Forgejo #FLOSS #FOSS

Which container images is everbody using for running Nix related jobs in Forgejo Actions?

I cobbled together some container images which include Node.js for running most unmodified upstream actions, but I'm wondering if I just missed some great pre-existing ones.

🔗 https://github.com/joschi/forgejo-runner-nix-containers/

#forgejo #ForgejoActions #codeberg #containers #nix #nixos

So I'm trying to use Forgejo Actions. I defined a job to run inside a OCI container that has the build tool I need. The Action to checkout the repository does not work because it expects nodejs to exist in that container? Also can't share the file system between jobs. Also can't install nodejs in that build container because it doesn't include a package manager (which is fine normally).

I've seen some comments that recommend to build and publish a custom container that includes both the tool I need and nodejs, but surely that can't be the solution.

I don't understand how this is supposed to work? If someone knows how this Action system is intended to be used I'd be grateful.

#Forgejo #ForgejoActions

I’m very interested in moving my 11ty deployment from GitHub to the omg.lol SourceTube (M$ and AI etc🤮).

It seems like I’d mainly need to figure out the Actions Runner to build and publish to my host NeoCities.

https://home.omg.lol/info/forge

#11ty #SourceTube #Forgejo #ForgejoActions #NeoCities

In an EPIC bout of yak-shaving I have reduced the build time for this static site infrastructure running on a puny VPS by a factor of 5. Come along on this undiagnosed journey.

Anatomy of a yak-shave:

• See what had happened was...
• I wanted to put animated snowflakes on my site
• Learned about CSS animation, nice
• Learned how to not bork screen readers
• Remembered I barely got my CI/CD working with Forgejo runner
• Remembered it takes for ever to deploy
• Realized most of it is just downloading and setting up dependencies
• How hard can it be to bake all that into my own image?
• Oh Forgejo supports a container registry too, nice!
• If I can't quickly build and push an image then this will have to wait
• Oh wow, that was really easy
• False sense of how well things are going
• All the freaking examples are for using public forges with public container registries
• Fall down several totally wrong rabbit holes due to lack of knowledge
• Have not stood up, eaten, drank, blinked in hours by this point
• Things are kinda working, yay! Noooo version mismatch
• I barely know Nix flakes, how do channels work, how do you pin them?
• Realized my tools have been broken but flake.lock has been saving me, nice!
• Fatigue related silly errors and utter faith this attempt will work so I don't need to make a quick test setup and test on a much faster setup
• Revert back to how it was, drink water, oh wait silly me...
• Victory
• Should probably write a blog post, it'll be SO fast to deploy

#Forgejo #CICD #ForgejoActions #NixOS #YakShaving

Our hosted #ForgejoActions now have a `medium` runner available with 10 minutes timeout. Take a look at the announcement: https://codeberg.org/actions/meta/issues/3#issuecomment-8339199

Hosted Forgejo Actions is our second hosted CI/CD next to the existing #WoodpeckerCI which already has more generous limits.

Developers self hosting their Forgejo instances, or using another instance and need to setup an actions runner may find this new blog post useful :blobcatderpy:

We setup a forgejo runner with rootless podman in fedora!

https://blog.hachem.dev/setting-up-forgejo-runner-in-a-fedora-server-with-rootless-podman/

#Fedora42 #selfhosting #ForgejoActions #rootless #podman

Developers self hosting their Forgejo instances, or using another instance and need to setup an actions runner may find this new blog post useful :blobcatderpy:

We setup a forgejo runner with rootless podman in fedora!

https://blog.hachem.dev/setting-up-forgejo-runner-in-a-fedora-server-with-rootless-podman/

#Fedora42 #selfhosting #ForgejoActions #rootless #podman

Developers self hosting their Forgejo instances, or using another instance and need to setup an actions runner may find this new blog post useful :blobcatderpy:

We setup a forgejo runner with rootless podman in fedora!

https://blog.hachem.dev/setting-up-forgejo-runner-in-a-fedora-server-with-rootless-podman/

#Fedora42 #selfhosting #ForgejoActions #rootless #podman

Developers self hosting their Forgejo instances, or using another instance and need to setup an actions runner may find this new blog post useful :blobcatderpy:

We setup a forgejo runner with rootless podman in fedora!

https://blog.hachem.dev/setting-up-forgejo-runner-in-a-fedora-server-with-rootless-podman/

#Fedora42 #selfhosting #ForgejoActions #rootless #podman

Developers self hosting their Forgejo instances, or using another instance and need to setup an actions runner may find this new blog post useful :blobcatderpy:

We setup a forgejo runner with rootless podman in fedora!

https://blog.hachem.dev/setting-up-forgejo-runner-in-a-fedora-server-with-rootless-podman/

#Fedora42 #selfhosting #ForgejoActions #rootless #podman

Finally migrated my personal website (powered by #HugoSSG) from #GitLab to #Codeberg. Including #CI via #ForgejoActions and hosting via #CodebergPages. Jobs are running on the local #homelab server.

There are jobs for building and deploying the website and for updating the contribution data through #contripy.

So far this has been very smooth and straightforward. Though I still need to learn the new CI workflow syntax as I'm used to GitLab from the daytime job.

#Forgejo #FOSS #gitforge

so... if i'm understanding this right...

https://code.forgejo.org/forgejo/runner/src/commit/5f3ff3d2e2020b0ca16dfae69baa5adbfff62160/act/schema/workflow_schema.json#L1553

secrets cannot be used in a jobs.<job_id>.strategy.matrix block... but vars, the same thing but not hidden, can? :neocat_think:

i wonder if it's intended for some security reason i am not aware of, if there's some kind of technical limitation to implement it, or if it's a bug

#Forgejo #ForgejoActions

After yesterday's success of setting up a Foregejo Runner with Codeberg the problems started.

I'm working on a Local Action to upload files to FTP. It consists of action.yml, Dockerfile and entrypoint.sh but no change to any of these files triggers a rebuild of the Image. So, I'm stuck with the first built Image version, unless I shell into the Docker-in-Docker container and remove the Image manually.

This feels like either a caching issue or I am missing something obvious.

#forgejo #ForgejoActions #codeberg

I added second #adguard node that shares the same codebase, but I wanted to have only one codebase (not just copied), so I set CI/CD workflow using #ForgejoActions on @Codeberg

RT: https://mastodon.social/@cichy1173/114347148630845939

Weaving together my existing #selfhosted services to publish a university course schedule (https://tos.kultwiki.net/) from a #forgejo git repository (https://learn.kultwiki.net/thomas/TOSV25). #ForgejoActions start #mkdocs and the result is rsynced to #NginxProxyManager, which serves it as static pages. Took a while to figure out how to run actions across docker containers but it is always rewarding to streamline workflows while retaining complete control.

#plaintext #infrastructuring #selfhosting

Weaving together my existing #selfhosted services to publish a university course schedule (https://tos.kultwiki.net/) from a #forgejo git repository (https://learn.kultwiki.net/thomas/TOSV25). #ForgejoActions start #mkdocs and the result is rsynced to #NginxProxyManager, which serves it as static pages. Took a while to figure out how to run actions across docker containers but it is always rewarding to streamline workflows while retaining complete control.

#plaintext #infrastructuring #selfhosting

Weaving together my existing #selfhosted services to publish a university course schedule (https://tos.kultwiki.net/) from a #forgejo git repository (https://learn.kultwiki.net/thomas/TOSV25). #ForgejoActions start #mkdocs and the result is rsynced to #NginxProxyManager, which serves it as static pages. Took a while to figure out how to run actions across docker containers but it is always rewarding to streamline workflows while retaining complete control.

#plaintext #infrastructuring #selfhosting

Weaving together my existing #selfhosted services to publish a university course schedule (https://tos.kultwiki.net/) from a #forgejo git repository (https://learn.kultwiki.net/thomas/TOSV25). #ForgejoActions start #mkdocs and the result is rsynced to #NginxProxyManager, which serves it as static pages. Took a while to figure out how to run actions across docker containers but it is always rewarding to streamline workflows while retaining complete control.

#plaintext #infrastructuring #selfhosting

Weaving together my existing #selfhosted services to publish a university course schedule (https://tos.kultwiki.net/) from a #forgejo git repository (https://learn.kultwiki.net/thomas/TOSV25). #ForgejoActions start #mkdocs and the result is rsynced to #NginxProxyManager, which serves it as static pages. Took a while to figure out how to run actions across docker containers but it is always rewarding to streamline workflows while retaining complete control.

#plaintext #infrastructuring #selfhosting

@Codeberg first one is your service #CodebergPages and the other is #WoodpeckerCI

Also recently started using #ForgejoActions for deploying my website stuff.

A piece of criticism to all code forges I know: why not run #CI on all commits?

A bad commit is a liability. It will break bisect and make debugging miserable.

#ForgejoActions takes it to the extreme and cancels an already running action when I push another change.

I get it - it's too slow and expensive to test them all when pipelines take minutes to run. But you could just pause the old ones until the newest one is finished!

#testing #forgejo #gitea #gitlab #Codeberg #coding

Disappointed by #ForgejoActions :

the runner does not clone the repository for you. You need to explicitly add a line:

"- uses: actions/checkout@v4"

...and then

> Error: crun: executable file `node` not found in $PATH: [...]

Do I *really* need js to do a #Git checkout? Sheesh.

So here you go, the equivalent:

- run: git clone --depth 1 ${{ github.server_url }}/${{ github.repository }} -b ${{ github.ref_name }} .

#forgejo #ci #git

Testing WordPress plugins using Forgejo Actions

Preface: Almost all public WordPress plugin development takes place on GitHub. We also collaborate on GitHub. However, we want to use and promote free alternatives for our own project. We currently host our own forgejo instance, but have been thinking about moving our repositories to @Codeberg, where we are more likely to find contributors and bug reports until the forgejo federation is more mature.

Automated Testing Workflows: It took us a long time to set up working workflows that run integrations tests with WordPress and the WordPress ActivityPub-plugin within Forgejo Actions using the Forgejo-Runner. Copy pasting the GitHub Actions workflow from for instance the ActivityPub plugin was just the beginning of an almost ten hour long debugging session. But now the tests are working.

#ForgejoActions #ForgejoRunner #Forgejo #PHPCS #PHPUnit #WordPress

In the next iteration of my app i want to have proper test and CI for x86_64 and arm64.
So the next steps will be:
- try out #testcontainers to provide a #VaultWarden instance
- maybe send a PR with said container definition upstream
- get the CI running according to the #Relm4 documentation. That said i need to convert the actions used in the example to #ForgejoActions since i am hosting on #CodeBerg.

Then i will work on more features like the password dialog and the detail page.

In the next iteration of my app i want to have proper test and CI for x86_64 and arm64.
So the next steps will be:
- try out #testcontainers to provide a #VaultWarden instance
- maybe send a PR with said container definition upstream
- get the CI running according to the #Relm4 documentation. That said i need to convert the actions used in the example to #ForgejoActions since i am hosting on #CodeBerg.

Then i will work on more features like the password dialog and the detail page.

In the next iteration of my app i want to have proper test and CI for x86_64 and arm64.
So the next steps will be:
- try out #testcontainers to provide a #VaultWarden instance
- maybe send a PR with said container definition upstream
- get the CI running according to the #Relm4 documentation. That said i need to convert the actions used in the example to #ForgejoActions since i am hosting on #CodeBerg.

Then i will work on more features like the password dialog and the detail page.

In the next iteration of my app i want to have proper test and CI for x86_64 and arm64.
So the next steps will be:
- try out #testcontainers to provide a #VaultWarden instance
- maybe send a PR with said container definition upstream
- get the CI running according to the #Relm4 documentation. That said i need to convert the actions used in the example to #ForgejoActions since i am hosting on #CodeBerg.

Then i will work on more features like the password dialog and the detail page.

In the next iteration of my app i want to have proper test and CI for x86_64 and arm64.
So the next steps will be:
- try out #testcontainers to provide a #VaultWarden instance
- maybe send a PR with said container definition upstream
- get the CI running according to the #Relm4 documentation. That said i need to convert the actions used in the example to #ForgejoActions since i am hosting on #CodeBerg.

Then i will work on more features like the password dialog and the detail page.