You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the instructions at https://docs.gitea.io/en-us/reverse-proxies/ for setting up to serve static resources doesn't work. Currently, if you check out the repo, or grab a snapshot of master, and run make webpack, many required files aren't generated (see attached screenshot for missing resources).
I discovered via experimentation, that if I checked out the v.1.11.4 tag and ran make frontend (make webpack not being available), that worked.
I wonder if the documentation has been updated to reflect changes in a forthcoming release, so they'll become correct at some point? Filing this bug mainly so, if others get stuck in the same situation, they will learn of the workaround...
Screenshots
The text was updated successfully, but these errors were encountered:
Unfortunately we don't maintain a per-release docs version, so as you've said, things get confusing at some point. We've heavily rewritten the build procedure several times during the development of 1.12 (and it can still change a little more!), so the docs are kind of in a state of flux about that.
Gitea version 1.11.4 built with GNU Make 4.1, go1.13.9 : bindata, sqlite, sqlite_unlock_notify
[x]
):Description
Following the instructions at https://docs.gitea.io/en-us/reverse-proxies/ for setting up to serve static resources doesn't work. Currently, if you check out the repo, or grab a snapshot of
master
, and runmake webpack
, many required files aren't generated (see attached screenshot for missing resources).I discovered via experimentation, that if I checked out the
v.1.11.4
tag and ranmake frontend
(make webpack
not being available), that worked.I wonder if the documentation has been updated to reflect changes in a forthcoming release, so they'll become correct at some point? Filing this bug mainly so, if others get stuck in the same situation, they will learn of the workaround...
Screenshots
The text was updated successfully, but these errors were encountered: