wxiaoguang 50a72e7a83 Use a general approach to access custom/static/builtin assets (#24022) ... The idea is to use a Layered Asset File-system (modules/assetfs/layered.go) For example: when there are 2 layers: "custom", "builtin", when access to asset "my/page.tmpl", the Layered Asset File-system will first try to use "custom" assets, if not found, then use "builtin" assets. This approach will hugely simplify a lot of code, make them testable. Other changes: * Simplify the AssetsHandlerFunc code * Simplify the `gitea embedded` sub-command code --------- Co-authored-by: Jason Song <i@wolfogre.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>		2023-04-12 18:16:45 +08:00
..
admin_auth_ldap_test.go
admin_auth_ldap.go
admin_user_change_password.go
admin_user_create.go
admin_user_delete.go
admin_user_generate_access_token.go
admin_user_list.go
admin_user_must_change_password.go
admin_user.go
admin.go
cert.go
cmd.go
convert.go
docs.go
doctor.go
dump_repo.go
dump.go
embedded.go	Use a general approach to access custom/static/builtin assets (#24022)	2023-04-12 18:16:45 +08:00
generate.go
hook_test.go
hook.go
keys.go
mailer.go
main_test.go
manager_logging.go
manager.go
migrate_storage_test.go
migrate_storage.go
migrate.go
restore_repo.go
serv.go
web_acme.go
web_graceful.go
web_https.go
web.go