ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #forgejo
Step‑by‑step guide to diagnose and fix LDAP login problems in a self‑hosted Forgejo instance.
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.
Repository mirroring with private targets Forgejo 2.x allows a repository to push changes automatically to an external URL. When the target is a private repository, an access token must be supplied in the URL, e.g. https://token@host/path.git . The mirroring configuration accepts this form, but the documentation does not describe how the token is stored, pro
When running a Forgejo instance that authenticates users against an external LDAP directory, administrators often aim to apply the principle of least privilege by granting only the permissions required for each role. At the same time, they need to ensure that user accounts whose LDAP passwords have expired are not allowed to log in, even if the account still
The goal is to quantify how Forgejo's [service] PAGINATION_LIMIT setting influences API response throughput when listing repositories, issues, or pull requests. This configuration determines the maximum number of items returned per page, and its value may shift workload distribution across server resources such as database query time, memory allocation, and
I'm running a Forgejo instance (v1.21-era configuration) that regularly serves large repository pushes and LFS transfers, and I need to decide how to protect the server without breaking legitimate long-running operations. From the documentation, the [server] section in app.ini exposes ReadTimeout , ReadHeaderTimeout , and WriteTimeout , enforced globally by
Forgejo utilizes an internal database migrator that runs automatically on application startup to apply schema changes. This migrator requires writable database access and typically assumes exclusive use of the database to ensure data consistency during the upgrade process. The standard operational pattern for upgrades is a stop-service, replace binary, and s
Migrating a Small Application from GitHub to Forgejo The goal is to move the repository while keeping the application online, preserving webhooks, CI pipelines, and branch protection rules. Constraints include the lack of an automated bulk webhook export, the need to manually recreate branch protection settings, and the temporary database lock required for a
Goal is to receive mention and push alerts while suppressing low-priority events such as new user joins or repository creation without creating notification noise. Global notification preferences allow disabling email for event types across all repositories. This reduces noise universally but can cause missed alerts where the event type is relevant in a spec
git
github