⚒ Alfred Forge › Documentation

Alfred Forge Documentation

Alfred Forge is the sovereign source-code platform of the Perez Kingdom — sealed, self-hosted, and free for all humanity. It runs on AKJV-compliant infrastructure under alfredlinux.com.

Single sign-on: every Forge account is linked to your GoSiteMe identity. Sign in with Google or GoSiteMe — your PIN is required on every fresh sign-in.

Signing In

Two providers are available on the login page:

  • GoSiteMe — direct OAuth via your GoSiteMe account
  • Google — Google account, auto-linked to your GoSiteMe identity

After OAuth completes, Forge will ask for your commander PIN before any repository action.

Creating a Repository

  1. Click + → New Repository in the top right
  2. Choose owner (you or an org), name, and visibility
  3. Optionally initialize with README, .gitignore, license
  4. Click Create Repository

Clone over HTTPS:

git clone https://alfredlinux.com/forge/<owner>/<repo>.git

Or SSH (after uploading a key under Settings → SSH Keys):

git clone git@alfredlinux.com:<owner>/<repo>.git

Git Basics

git add .
git commit -m "covenant: initial work"
git push origin main

Use git pull to fetch upstream changes before pushing.

Hooks & Webhooks

Each repository has three hook types:

  • Git hooks — server-side scripts (pre-receive, update, post-receive). Configure under Settings → Git Hooks.
  • Webhooks — HTTP callbacks fired on push/PR/issue events. Configure under Settings → Webhooks.
  • Deploy keys — read-only or read-write SSH keys scoped to one repo.

Forge Actions

Actions run in .forgejo/workflows/ or .gitea/workflows/ at the root of your repo. They are CI workflows compatible with the GitHub Actions schema.

Enable them under Repository Settings → Actions → Enable Actions.

Push hook / Webhook / Actions aren't running?

If you see a banner saying "Git hooks of this repository seem to be broken", it usually means one of:

  1. Hook scripts are missing from the bare repo's hooks/ directory. Run git update-server-info on the server, or push any commit to refresh.
  2. File permissions wrong — hooks must be executable and owned by the forge user.
  3. Repo was imported from another platform without copying hook scripts.

To force a refresh: push any new commit, or contact a Forge administrator to run gitea admin regenerate hooks.

PIN & Security

Your commander PIN is set in GoSiteMe → Commander Vault. Forge requires it on every fresh sign-in (the PIN cookie expires after 15 minutes).

To change your PIN: GoSiteMe → Commander Vault → Change PIN.

API Tokens

Generate personal access tokens under Settings → Applications. Use them as the password in git clone or in API calls:

curl -H "Authorization: token <your-token>" \
  https://alfredlinux.com/forge/api/v1/user