Pages, but as subdir rather than subdomain #2962

New Issue

GiteaMirror · 2025-11-02T04:55:25-06:00

GiteaMirror commented

2025-11-02 04:55:25 -06:00

Originally created by @andrewgdunn on GitHub (Feb 22, 2019).

Pages has been proposed in several other issues, to enumerate some:

However there is an assumption that you must use subdomains as this is how github/gitlab have implemented them. Some are suggesting bundling of caddy (e.g. #1721) but this is making a choice for people that is uncomfortable (e.g. I enjoy running a simple go binary behind nginx for tls termination, I don't particularly want nginx->caddy->gitea or to learn/use caddy for just gitea)

Rightfully proposed by @techknowlogick in #302, if you're going to do subdomain pages you might as well work that through the CI route. However many users are going to be interested in static page hosting without having a CI system.

It could be possible to run these pages as subdirectories, maybe with a prefix of ~/ of some kind where ~/organization provides a static page for the organization and ~/organization/repo does the same for repo (switch organization for user), with some complexity in access control (e.g. don't show static pages to users who have not logged in, if that's the intent).

So, this can me marked dupe and closed, but I'll offer one twist:

This is an interesting feature and we'd be willing to fund it directly. We cannot bounty-source and we cannot easily donate to the project but we can contract directly with a developer(s) who want to take this work on as long as you propose a plan that upstream is willing to bite on. It would be the lowest risk for us to work with proven contributors or maintainers of this project.

Originally created by @andrewgdunn on GitHub (Feb 22, 2019). Pages has been proposed in several other issues, to enumerate some: - #302 - #2208 - #3834 However there is an assumption that you must use subdomains as this is how github/gitlab have implemented them. Some are suggesting bundling of caddy (e.g. #1721) but this is making a choice for people that is uncomfortable (e.g. I enjoy running a simple go binary behind nginx for tls termination, I don't particularly want nginx->caddy->gitea or to learn/use caddy for just gitea) Rightfully proposed by @techknowlogick in #302, if you're going to do subdomain pages you might as well work that through the CI route. However many users are going to be interested in static page hosting without having a CI system. It could be possible to run these pages as subdirectories, maybe with a prefix of `~/` of some kind where `~/organization` provides a static page for the organization and `~/organization/repo` does the same for repo (switch `organization` for `user`), with some complexity in access control (e.g. don't show static pages to users who have not logged in, if that's the intent). So, this can me marked dupe and closed, but I'll offer one twist: This is an interesting feature and we'd be willing to fund it directly. We cannot bounty-source and we cannot easily donate to the project but we can contract directly with a developer(s) who want to take this work on as long as you propose a plan that upstream is willing to bite on. It would be the lowest risk for us to work with proven contributors or maintainers of this project.

GiteaMirror added the issue/stale label 2025-11-02 04:55:25 -06:00

GiteaMirror closed this issue

2025-11-02 04:55:25 -06:00

GiteaMirror commented

2025-11-02 04:55:26 -06:00

@lunny commented on GitHub (Feb 23, 2019):

There are some security reasons to be consider when using subdir than subdomain.

@lunny commented on GitHub (Feb 23, 2019): There are some security reasons to be consider when using subdir than subdomain.

GiteaMirror commented

2025-11-02 04:55:26 -06:00

@stale[bot] commented on GitHub (Apr 24, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 24, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:55:26 -06:00

@sblisesivdin commented on GitHub (May 5, 2019):

I think even a static page website thing is not necessary. Wiki feature can be used to built sites with subdir. The thing is people want to host documentation and project related websites with this. No need to repeat the GitHub or GitLab on this feature.

@sblisesivdin commented on GitHub (May 5, 2019): I think even a static page website thing is not necessary. Wiki feature can be used to built sites with subdir. The thing is people want to host documentation and project related websites with this. No need to repeat the GitHub or GitLab on this feature.

GiteaMirror referenced this issue

2025-11-02 12:16:24 -06:00

[PR #2973] [MERGED] Fix error when add user has full name to team #16688

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2962