gitea: Release builds don't seem to serve js/css
Don’t think we have an issue on this one yet:
The master release builds https://dl.gitea.io/gitea/master/ seem to have some issue serving js/css and instead serve either a 404 or redirect to /install depending on the INSTALL_LOCK setting.
I see no issue in the relevant drone steps, they do seem to complete fine and files should be generated and generate definitely runs (as part of the release dependencies):
https://drone.gitea.io/go-gitea/gitea/17228/3/3 https://drone.gitea.io/go-gitea/gitea/17228/3/4
When I run make release locally, it does produce working binaries, so I think the issue is something specific to drone. I’m not sure how to troubleshoot further without access to a drone server. I’d attempt a merge of the relevant steps like https://github.com/go-gitea/gitea/pull/9316, but drone documentation says that files are shared between steps, so it may not help.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (13 by maintainers)
@ashimokawa fixed your issue in https://github.com/go-gitea/gitea/pull/9338 as well, now it won’t make a difference whether you run
make generate buildormake build.make generate buildmay cause a wrong order of execution which leads to missing webpack files. It’s best to always usemake build.@gsantner your issue is a duplicate to this one. It was caused by https://github.com/go-gitea/gitea/commit/d9c67a8c903fa9927bad28f5fcb816f89f8200eb, we will have a fix soon in https://github.com/go-gitea/gitea/pull/9338.