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
..
authorizedkeys.go
breaking.go
checkOldArchives.go
dbconsistency.go	Refactor setting.Database.UseXXX to methods (#23354)	2023-03-07 18:51:06 +08:00
dbversion.go
doctor.go	Refactor the setting to make unit test easier (#22405)	2023-02-20 00:12:01 +08:00
fix16961.go
fix16961_test.go
heads.go
lfs.go	Add cron method to gc LFS MetaObjects (#22385)	2023-01-16 13:50:53 -06:00
mergebase.go
misc.go	Rename repo.GetOwner to repo.LoadOwner (#22967)	2023-02-18 20:11:03 +08:00
paths.go	Use a general approach to access custom/static/builtin assets (#24022)	2023-04-12 18:16:45 +08:00
storage.go	Check LFS/Packages settings in dump and doctor command (#23631)	2023-03-23 20:30:28 +08:00
usertype.go