Install Guide

This tool will install Git and Forgejo.

Select an unused address and click the "Set Up Git-cloud" button to begin the install and configure procedure. Forgejo will require full use of the domain assigned, so the address cannot be in use by a Web App, Static Files config, or Forwarding config.

Lifeboat will install Git with the package manager. Forgejo requires a non-root user so Lifeboat will create one named git. For security this account will be unable to log in via SSH which is a standard practice. Git authentication will be done with SSH Key Pairs configured through the Forgejo Web UI.

After the Git setup procedure, Lifeboat will download a specific version of Forgejo from the official Releases page. For safety and security Lifeboat will verify the hash against an internally bundled manifest. Please contact support if you need any assistance.

Lifeboat will launch your web browser with the Forgejo URL to complete setup once installation has finished. This will only happen automatically if the "Launch Web App in browser after deployment" setting is enabled. Otherwise, this may need to be done manually.

Forgejo Initial Configuration

Forgejo supports several database types but the install procedure does not automatically include any database servers. SQLite is the default database engine so that the Git-cloud feature will work "out of the box" for most cases. Please install the desired database server before completing initial configuration if SQLite will be insufficient.

For the best results, Lifeboat has pre-configured many settings and hidden them from view for simplicity. Expand each collapsable section under Optional Settings and review all the options.

Set these now, as they cannot be configured easily later.

With the initial settings configured and double-checked, click "Install Forgejo" to finish initial configuration. This may take a few seconds to complete.

Don't forget to upload a Public SSH Key to your Forgejo account for SSH Key Pair authentication. For extra security disable HTTP access. Be mindful of Fail2Ban, which will IP address ban anyone with too many failed SSH authentication attempts.