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.

Sign up for GitHub

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

Jump to bottom

Prevent collision naming with a gitea-vendor directory #8072

Closed
camlafit opened this issue Sep 3, 2019 · 1 comment
Closed

Prevent collision naming with a gitea-vendor directory #8072

camlafit opened this issue Sep 3, 2019 · 1 comment
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@camlafit
Copy link
Contributor

camlafit commented Sep 3, 2019 •
edited
Loading

Hello

To note a discussion with @sapk discord, could be interesting to use a root directory as gitea-vendor/ or web-vendor/ or any other path to store all statics resources.

Could be solve with a different way #20

Actual solution has two troubles :

  • we must manage an hardcoded reserved keyword (an some name could be licit account/organization)
  • An 500 error is raised without any information when we try to rename an organization with a keyword in this list.
@camlafit camlafit mentioned this issue Sep 3, 2019
Merged
@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Sep 3, 2019
@wxiaoguang
Copy link
Contributor

/assets is reserved and it's for static resources.

@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lunny @camlafit @wxiaoguang