How to Set Up a Self-Hosted Forgejo Actions CI/CD Runner with Docker-in-Docker

·1 views

Forgejo Actions enables automated CI/CD pipelines directly within a self-hosted Forgejo Git server, triggering tests and deployments on every code push. The setup relies on a self-operated runner paired with a Docker-in-Docker sidecar, which isolates each CI job in its own disposable container. Once configured, the runner registers globally with the Forgejo instance and executes workflows defined in the .forgejo/workflows/ directory. Forgejo Actions uses the same syntax as GitHub Actions, making existing workflow knowledge and many marketplace actions directly reusable. The guide was tested on Forgejo 16.0.3 and Runner v13.1.0 running on Debian 13 with Docker 29.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

DIY AI plush toy runs fully offline using Raspberry Pi and a local LLM

A developer has built an open-source AI-powered plush toy capable of holding philosophical conversations entirely on a local network without any internet connection. The toy uses a Raspberry Pi Zero WH paired with a USB microphone, camera, speaker, and a servo motor to move its head, with all processing handled by a connected computer running a local AI inference server. It can recognize multiple faces, detect emotions, remember past conversations, and respond with customizable personalities in English or Spanish. The full hardware build costs approximately €110, excluding the computer and inference server, and the project recommends at least an 8-billion-parameter language model. The source code is publicly available on GitHub under an MIT license, and the creator states the project is non-profit and collects no user data.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Google Gemini Now Officially Integrates with Webflow for AI-Powered CMS Workflows

Google Gemini has been added as a supported integration for Webflow, enabling website teams to incorporate AI-generated text, image analysis, and automated content pipelines into their projects. The integration offers three distinct implementation paths: a code-embed approach using a backend proxy for visitor-facing features, automation platforms like Zapier or Make for repeatable CMS and form-based workflows, and direct REST APIs for fully custom programmatic control. Webflow and Google both document the connection officially, with Webflow's integration page outlining the supported methods in detail. The integration is designed to assist with routine but time-consuming tasks such as drafting FAQ entries, writing product descriptions, or processing form submissions — not as a one-click, fully automated site builder. Teams are expected to handle server-side logic and human review, as the tools provide structured workflow support rather than end-to-end automation without oversight.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Software Needs State Machines: Lessons from an Order Fulfillment Model

A software design tutorial on DEV Community explores why applications must track not just data but system state to behave correctly. Using an e-commerce order fulfillment example, the author demonstrates that a single command like ship_order can require different actions depending on what has previously occurred. A naive implementation using a plain status string field can allow invalid transitions, such as shipping an unpaid order, because the field stores data without enforcing business rules. The tutorial distinguishes between ordinary data fields and a special 'state' field whose value actively governs what the system is allowed to do next. This distinction sets the conceptual foundation for introducing state machines as a principled solution to the problem.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Add Self-Service Ad Hoc Reporting to ASP.NET Core Apps

Developer Razi Syed has published a guide on embedding self-service ad hoc reporting into ASP.NET Core applications using the Dotnet Report NuGet package. The approach allows non-developers to build their own reports by selecting tables, columns, filters, and charts through a guided interface, eliminating the need for developers to write each report manually. Integration involves installing the package, configuring API tokens and a database connection string in appsettings.json, and registering the required MVC, session, and HttpClient services. Once the schema is exposed, users can independently create, export, schedule, and visualize reports without writing any SQL. The method is compatible with .NET 6 and above, with separate packages available for legacy .NET Framework MVC and Web Forms projects.

0 comments Read more at DEV Community