Skip to content

Customization files should not require /assets path segment #15906

New issue
New issue
Closed
Closed
Customization files should not require /assets path segment#15906
Labels
skip-changelogThis PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features.type/bug
Milestone
 
1.15.0
@silverwind

Description

@silverwind
silverwind
opened on May 17, 2021

Since #15219, previous customization files like $GITEA_CUSTOM/public/img/logo.svg are not loaded any more and require $GITEA_CUSTOM/public/assets/img/logo.svg to be loaded again, we should fix this because the assets segment should only be relevant on HTTP, not in the file system.

Metadata

Metadata

Assignees

No one assigned

    Labels

    skip-changelogThis PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features.type/bug

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions