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

Serving custom public files = stop working #16292

Closed
2 of 6 tasks
mariuszmaximus opened this issue Jun 29, 2021 · 4 comments · Fixed by #16337
Closed
2 of 6 tasks

Serving custom public files = stop working #16292

mariuszmaximus opened this issue Jun 29, 2021 · 4 comments · Fixed by #16337
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail topic/distribution This PR changes something about the packaging of Gitea type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@mariuszmaximus
Copy link

mariuszmaximus commented Jun 29, 2021

  • Gitea version (or commit ref): 1.15.0+dev-509-g2f3d3ac20
  • Git version: Git Version: 2.30.2, Wire Protocol Version 2 Enabled
  • Operating system: docker on ubuntu 19.10
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:

Description

...
In my opinion stop working "Serving custom public files" in "Customizing Gitea" https://docs.gitea.io/en-us/customizing-gitea/
I used gitea over "docker pull gitea/gitea"
a month ago it was working
when I put file to "$GITEA_CUSTOM/public/test.jpg" I can open it in http://my-gitea.com/test.jpg
a few days ago I updated and it stopped working

My current gitea
Using default tag: latest
latest: Pulling from gitea/gitea
Digest: sha256:b3011b077d5d2e8ce504755e2f373c86e784e30ce1068436a74f561de3f82a89
Status: Image is up to date for gitea/gitea:latest
docker.io/gitea/gitea:latest
0ab3ec073bb1d14b00779b0bfe2e0e287c504555323fa30a16b448a7d7e4d01f

@noerw
Copy link
Member

noerw commented Jul 1, 2021

It might be a file permission issue, if you're sure it's about the custom files in custom/public/.
We need gitea logs to get to the cause of this.

@noerw noerw added type/question Issue needs no code to be fixed, only a description on how to fix it yourself. issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail theme/docker labels Jul 1, 2021
@zeripath
Copy link
Contributor

zeripath commented Jul 2, 2021

I think this is related to the assets root pr

Try http://my-gitea.com/assets/test.jpg

@lunny
Copy link
Member

lunny commented Jul 2, 2021

PR #15219 move all assets under /assets

@mariuszmaximus
Copy link
Author

I confirm
$GITEA_CUSTOM/public/test.jpg is on http://my-gitea.com/assets/test.jpg

Please update Serving custom public files

For example, a file image.png stored in $GITEA_CUSTOM/public/, can be accessed with the url http://gitea.domain.tld/image.png

to:

For example, a file image.png stored in $GITEA_CUSTOM/public/, can be accessed with the url http://gitea.domain.tld/assets/image.png

@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
@delvh delvh added topic/distribution This PR changes something about the packaging of Gitea and removed theme/docker labels Oct 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail topic/distribution This PR changes something about the packaging of Gitea type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants