Assets for customizing forgejo

The file hierachy of the assets themselves are as follows.

.
├── public
│   └── assets
│       ├── css
│       │   ├── base.css                   (default of base.css from the forgejo main repo)
│       │   └── overrides.css              (overrides of fonts, etc.)
│       └── img
│           └── undead-transparent.png     (logo for home page and navbar)
├── README.md
└── templates
    ├── base
    │   ├── head_navbar.tmpl    (navbar override)
    │   └── head_style.tmpl     (head for importing css)
    │   └── head.tmpl           (setting the logo in the head)
    └── home.tmpl               (main page for non-logged-in users)
7 directories, 7 files

Container tips

The public and templates directories has to be mounted in the $custom_path for forgejo, which is usually /data/gitea. So including the following in a docker compose deployment would work.

    volumes:
        - ./templates:/data/gitea/templates
        - ./public:/data/gitea/public

Volume management for a podman quadlet deployment could be done with adding the following to the quadlet example from the forgejo documentation.

Volume=%h/public:/data/gitea/public:U,Z
Volume=%h/templates:/data/gitea/templates:U,Z

The :U and Z suffixes can be read more about in podman's documentation. The brief summary from the documentation is:

• "The :U suffix tells Podman to use the correct host UID and GID based on the UID and GID within the container, to change recursively the owner and group of the source volume. (...)"
• "The Z option tells Podman to label the content with a private unshared label. Only the current container can use a private volume." for SELinux purposes.

Licensing

The templates and css are taken from the forgejo source-code and as such remains under their original license (GPLv3). The images and other assets stored in public/assets/img are under the Creative Commons CC0 license, which is included in the directory.