The Wayback Machine - https://web.archive.org/web/20200521033715/https://github.com/go-gitea/gitea/issues/11201
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reverse proxy setup instructions are incorrect #11201

Open
genehack opened this issue Apr 24, 2020 · 1 comment
Open

reverse proxy setup instructions are incorrect #11201

genehack opened this issue Apr 24, 2020 · 1 comment
Labels

Comments

@genehack
Copy link

@genehack genehack commented Apr 24, 2020

  • Gitea version (or commit ref): Gitea version 1.11.4 built with GNU Make 4.1, go1.13.9 : bindata, sqlite, sqlite_unlock_notify
  • Git version: 2.20.1
  • Operating system: Debian
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

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 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

Screen Shot 2020-04-23 at 21 03 11

@guillep2k guillep2k added the kind/docs label Apr 25, 2020
@guillep2k
Copy link
Member

@guillep2k guillep2k commented Apr 25, 2020

Duly noted.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.