GLWS · Developer tools
Run a community-focused Git forge for repositories, issues and collaborative development.
Common uses of Forgejo.
Check the documentation for the release you install. Repository hosting and optional action runners need separate resource and permission planning.
Planning examples, not official minimum requirements.
Developer tools
Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.
Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.
Read the Forgejo documentation ↗ (opens in a new tab)Advice specific to this application.
Decide whether registration is open, restricted or administrator-managed, and how contributors will authenticate. Plan storage for repositories, attachments and packages alongside the database. Published project visibility and administrator permissions should be deliberate choices.
Optional runners execute project-defined commands, so treat them as a distinct service with its own credentials and limits. Record the installed Forgejo version and retain configuration, repositories and database backups together. Check upgrade notes before changing release series.
Linux guides that help with this setup.
Generate a key on your computer, install its public half, and verify a fresh login before changing authentication settings.
Read guide →Read the basic resource indicators on Ubuntu 24.04 LTS and AlmaLinux 9, then identify where to investigate a slowdown.
Read guide →Create a compressed archive of your own project, verify it, and extract a test copy without overwriting the original files.
Read guide →Four steps that make the environment easier to maintain.
Read the publisher's instructions and choose a supported installation method.
Protect the dashboard, credentials and network endpoints before you expose any service.
Work out where the application keeps its state and store it separately from replaceable runtime files.
Back up the data and configuration, then check that you can restore them.
Run through it before and after you install.
$ application-checklist --name forgejo
[ ] Supported deployment method
[ ] Authentication and access restrictions
[ ] Independent data backup
[ ] Updates and restoration tested
root@glws:~#
Quick answers before you choose resources.
No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.
Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.
You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.
The knowledge base covers Linux access, packages, services, firewalls and backups.
Other tools you might run alongside or instead.
Host Git repositories, issues and code review in a compact development workspace.
Explore application →Website, email, DNS and database management in a hosting dashboard.
Explore application →A self-hosted assistant for connecting model-powered tasks with tools and messaging.
Explore application →An agent workspace for conversations, tools and automation on infrastructure you control.
Explore application →