reverse proxy setup instructions are incorrect #5300

New Issue

GiteaMirror · 2025-11-02T06:20:50-06:00

GiteaMirror commented

2025-11-02 06:20:50 -06:00

Originally created by @genehack on GitHub (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

Originally created by @genehack on GitHub (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 - [X] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] 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 <img width="1092" alt="Screen Shot 2020-04-23 at 21 03 11" src="https://user-images.githubusercontent.com/42126/80174768-8aecdc00-85a8-11ea-9daf-fb41d3a5f20d.png">

GiteaMirror added the type/docs label 2025-11-02 06:20:50 -06:00

GiteaMirror closed this issue

2025-11-02 06:20:50 -06:00

GiteaMirror commented

2025-11-02 06:20:52 -06:00

@guillep2k commented on GitHub (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.

@guillep2k commented on GitHub (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.

GiteaMirror referenced this issue

2025-11-02 15:28:52 -06:00

[PR #5300] [MERGED] Fix file edit change preview functionality #17746

GiteaMirror referenced this issue

2025-11-02 15:30:53 -06:00

[PR #5311] [MERGED] Fix file edit change preview functionality (#5300) #17752

Sign in to join this conversation.