ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Forgejo’s native support for external runners lets you run CI/CD pipelines on your own hardware. This guide walks through configuring a self‑hosted runner, adding a simple workflow, and highlights trade‑offs such as resource use and token security.
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.
An architecture note for a minimal Forgejo Actions deployment: one forge, one isolated Docker runner, the trust boundaries that matter, and the failure modes to test before they surprise you.
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
Bitbucket Data Center ties supported Java major version to specific product releases. The supported range changes across major and minor versions, so a supported deployment requires a documented pairing of Data Center release and Java runtime. Upgrading across Java major versions is constrained by release-specific support boundaries and by plugin and third-p
In self-hosted Gitpod, operators provide wildcard DNS and TLS certificates for the ingress that fronts workspace hosts. When those certificates are signed by a private certificate authority, the trust boundary between the ingress and the workspace container becomes relevant. It is unclear whether custom CA certificates trusted by the Gitpod ingress are autom
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
forgejo
prisma
hoppscotch
bitbucket