Codeberg/Community
60
387
Fork
You've already forked Community
12

Turn Codeberg Pages into gitea-pages? #377

Closed
opened 2021年01月03日 08:49:54 +01:00 by circlebuilder · 7 comments

While I was reading #362, marked as bug, I felt that the PR was a bit of a bolt-on to something that is a workaround to missing Gitea functionality.

Isn't the issue really that Codeberg - with Gitea lacking a Github-like Pages feature of its own (i.e. with repo Settings UI for Pages) - came up with the workaround to have a "Pages" magic name to demarkate Pages repositories?

A possible solution being to turn the Codeberg Pages functionality in, idk, a Gitea plugin project maybe, offered on awesome-gitea, so its available all across the (gitea-)board, and for more people to add contrib?

Then other open issues (e.g. #303 #218 #115) with pending/proposed features can be addressed in that project.

While I was reading #362, marked as bug, I felt that the PR was a bit of a bolt-on to something that is a workaround to missing Gitea functionality. Isn't the issue really that Codeberg - with Gitea lacking a Github-like Pages feature of its own (i.e. with repo Settings UI for Pages) - came up with the workaround to have a "Pages" magic name to demarkate Pages repositories? A possible solution being to turn the Codeberg Pages functionality in, idk, a Gitea plugin project maybe, offered on [awesome-gitea](https://gitea.com/gitea/awesome-gitea), so its available all across the (gitea-)board, and for more people to add contrib? Then other open issues (e.g. #303 #218 #115) with pending/proposed features can be addressed in that project.

I'm personaly against this.
It should be a side project or eaven better implemented as a plugin

I'm personaly against this. It should be a side project or eaven better implemented as a plugin

Part of Gitea then, ideally, you mean to say.. or just as-is?

Edit: I mentioned Plugin. Not familiar with all the packaging options at hand.

Part of Gitea then, ideally, you mean to say.. or just as-is? **Edit**: I mentioned Plugin. Not familiar with all the packaging options at hand.

As a maintainer of gitea I see the codebase grow and grow - at some moint it's hard to maintain and keep clean ... or just say it in other words: I dont like to see gitea to become gitlab

As a maintainer of gitea I see the codebase grow and grow - at some moint it's hard to maintain and keep clean ... or just say it in other words: I dont like to see gitea to become gitlab

100% valid point. I think my first sentence may have put you off-track.. sorry, should have formulated better, because in your 1st follow-up comment was what I intended: a side-project and/or plugin that exists independent of Gitea main project, and that people just grab iif they want a Pages-like service.

100% valid point. I think my first sentence may have put you off-track.. sorry, should have formulated better, because in your 1st follow-up comment was what I intended: a side-project and/or plugin that exists independent of Gitea main project, and that people just grab iif they want a Pages-like service.
Owner
Copy link

I think, such a discussion shall be opened over at Gitea, explaining why more people than those using Codeberg (= users of other instances) need this feature. This is nothing, we should discuss here.

It'd of course be cool if someone would pick this up and provide a 'cleaner' implementation like a plugin for Gitea including some wanted features like more settings etc.

But currently there's a lot to do at Gitea and there are also some feature requests for Codeberg pages, I simply fear that there's no power for a re-implementation of the existing stuff anytime soon. Sorry. Of course open if someone wants to have a look at this.

I think, such a discussion shall be opened over at Gitea, explaining why more people than those using Codeberg (= users of other instances) need this feature. This is nothing, we should discuss here. It'd of course be cool if someone would pick this up and provide a 'cleaner' implementation like a plugin for Gitea including some wanted features like more settings etc. But currently there's a lot to do at Gitea and there are also some feature requests for Codeberg pages, I simply fear that there's no power for a re-implementation of the existing stuff anytime soon. Sorry. Of course open if someone wants to have a look at this.
Owner
Copy link

I think the way Moritz goes with the new codeberg-pages is a good one. Clean code base to add all the features on top (and get away from the simple hack as it was called here), and Gitea can concentrate on a reliable and feature-rich git hosting solution (since not everyone needs a pages feature ...).

I think the way Moritz goes with the new [codeberg-pages](/momar/codeberg-pages) is a good one. Clean code base to add all the features on top (and get away from the simple hack as it was called here), and Gitea can concentrate on a reliable and feature-rich git hosting solution (since not everyone needs a pages feature ...).

if it goes into deploy we can mention codeberg-pages on gitea docs :)

this way each project can focus on there core aims

if it goes into deploy we can mention codeberg-pages on gitea docs :) this way each project can focus on there core aims
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug
Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome
Please join the discussion and consider contributing a PR!
docs
No bug, but an improvement to the docs or UI description will help
duplicate
This issue or pull request already exists
enhancement
New feature
infrastructure
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal
An issue directly involving legal compliance
licence / ToS
involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations
Things related to Codeberg's external communication
question
More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo
Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration
Migration related issues in Forgejo
s/Pages
Issues related to the Codeberg Pages feature
s/Weblate
Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker
Woodpecker CI related issue
security
involves improvements to the sites security
service
Add a new service to the Codeberg ecosystem (instead of implementing into Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, etc.)
wontfix
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#377
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?