Conversation

Notices

1. Embed this notice
   Annika Backstrom (annika@xoxo.zone)'s status on Tuesday, 02-Jan-2024 08:45:35 JST Annika Backstrom

   • Gitea

   Did @gitea assets move recently? 🤔 I had to change `alias /path/to/gitea/public/` to `alias /path/to/gitea/public/assets/` in my nginx conf.

   https://docs.gitea.com/administration/reverse-proxies#single-node-and-single-domain

   #gitea

   • Embed this notice
     Annika Backstrom (annika@xoxo.zone)'s status on Tuesday, 02-Jan-2024 08:48:20 JST Annika Backstrom

     in reply to

     • Gitea

     @gitea Thanks!

   • Embed this notice
     Gitea (gitea@social.gitea.io)'s status on Tuesday, 02-Jan-2024 08:48:31 JST Gitea

     in reply to

     @annika yup. They were moved to a dedicated path in 1.21.0, if you’re interested in the reasoning you can find it here: https://blog.gitea.com/release-of-1.21.0#%EF%B8%8F-move-public-asset-files-to-the-proper-directory-25907

   • Embed this notice
     Annika Backstrom (annika@xoxo.zone)'s status on Tuesday, 02-Jan-2024 09:06:45 JST Annika Backstrom

     in reply to

     What tripped me up was that `make clean` didn't delete the old assets, so things were partially functional rather than assets immediately 404ing. This got me looking for problems in the build steps rather than the filesystem layout.