A team that wants continuous integration without a SaaS or Jenkins can use Forgejo Actions. This post explains how workflows live in .forgejo/workflows, how act_runner daemons pick up jobs via labels, shows a full example, and weighs the trade‑offs of owning the runner infrastructure.
Forgejo Actions lets you run CI/CD pipelines directly on your self‑hosted Forgejo instance. This post walks through enabling the feature, creating a simple workflow, and highlights the limitations of the native runner before scaling your CI/CD.
Context Hoppscotch self-hosted applies database schema changes through Prisma migrations tracked in the prisma/migrations directory. Prisma does not ship a built-in migrate rollback command, leaving administrators without a documented single-command path to revert a schema change safely. Constraints Reverting a migration currently requires either authoring a
Proxy Path Selection for Cross-Origin Requests Hoppscotch's web client cannot directly issue arbitrary cross-origin API calls from the browser, making the Proxy setting a practical requirement for many workflows. The application exposes a toggle that routes requests through a hosted intermediary to bypass CORS limits without a browser extension, alongside su
When upgrading a self-hosted Gitpod installation via Helm, pre-upgrade hooks execute PostgreSQL schema migrations. If the upgrade fails after migrations have partially applied, Helm's rollback reverts only Kubernetes resources, leaving the database schema in an altered state. The official documentation advises taking a full database backup before upgrading b
Interoperability boundary The self-hosted Appwrite stack pins its release through the _APP_VERSION variable in the generated .env file, while persistent state — especially the MariaDB data volume — survives container replacement. An upgrade runs docker compose exec appwrite migrate inside the new API container, which applies forward-only schema changes to th