fluxerapp/fluxer
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
d977b3563686fa334f2c446cff31232befb24e8e
fluxer/NOTES.md
Kitty Cat d977b35636
Some checks failed
release server / resolve build metadata (push) Successful in 12s
Details
release server / build fluxer server (push) Failing after 3m40s
Details
release server / create release (push) Has been skipped
Details
release server / release summary (push) Failing after 5s
Details
test cassandra-backup / Test latest Cassandra backup (push) Has been cancelled
Details
fix: use registry_token secret for Gitea authentication 
Gitea doesn't allow secrets with GITEA_ or GITHUB_ prefixes.
Using registry_token secret instead.
2026-03-01 10:51:58 -05:00

2.9 KiB
Raw Blame History

uwu.lc Self-Hosting Notes

Branch Setup

Current branch: uwu (based on refactor)

  • Tracks: origin/refactor for rebasing upstream changes
  • Pushes to: i5/uwu on your Gitea instance at git.i5.wtf
  • Current state: 1 commit ahead (LFS config change)

Workflow

Pull upstream changes and rebase

git fetch origin
git rebase origin/refactor

Push your changes to Gitea

git push i5 uwu
# If you've rebased, use: git push i5 uwu --force-with-lease

View your changes

git log origin/refactor..uwu  # Show commits you've added

Why track refactor branch?

The refactor branch is a complete rewrite that:

  • Is simpler and lighter to self-host
  • Uses SQLite instead of complex database setup
  • Removes payment/Plutonium stuff for self-hosted deployments
  • Is much better documented
  • Is where active development happens

The old main/canary branches have the legacy stack that's harder to self-host.

Configuration Changes Made

  1. LFS Config (.lfsconfig): Updated to point to Gitea instance

    • Old: https://github.com/fluxerapp-old/fluxer-private.git/info/lfs
    • New: https://git.i5.wtf/fluxerapp/fluxer.git/info/lfs

  2. CI Workflows: Updated for Gitea compatibility

    • Changed all runners from blacksmith-8vcpu-ubuntu-2404 to ubuntu-latest
    • ci.yaml: Main CI workflow (typecheck, test, gateway, knip, ci-scripts)
    • release-server.yaml: Docker build workflow
      • Registry: ghcr.io → git.i5.wtf
      • Image: fluxerapp/fluxer-server
      • Trigger branch: canary → uwu
      • Default source ref: canary → uwu

Gitea Setup Requirements

Container Registry Authentication

The workflow tries to use secrets.GITEA_TOKEN or github.token for registry auth.

Required: Create a Gitea Personal Access Token:

  1. Go to Gitea Settings → Applications → Generate New Token
  2. Name: CI_Container_Registry
  3. Permissions: Select package (write access)
  4. Add to repository secrets as registry_token (Note: Can't use GITEA_ or GITHUB_ prefix)

Alternative: Update the workflow to use username/password:

  • Create a secret REGISTRY_USERNAME with your Gitea username
  • Create a secret REGISTRY_PASSWORD with a personal access token

Container Registry URL Format

Gitea registry format is typically:

  • git.i5.wtf/fluxerapp/fluxer-server:tag

If the registry requires a different format, check your Gitea container registry settings.

TODO

  • Modify GitHub Actions workflows for Gitea compatibility
  • Fix container registry authentication
  • Apply patches from third-party guide (if needed)
  • Configure for uwu.lc domain
  • Test CI on Gitea instance
  • Build Docker image
  • Deploy to production

Resources