Skip to content

Gitea hosted Gitea #1029

Open
Open

Description

@lunny

For the first big stage, we would like Gitea's development could be based on a Gitea hosted and github will only a mirror. This will maybe completed in v1.x. So that this issue will list all the features needed to be implemented before v1.x. And of course please discuss them and change my post.

Migrating Progress Updated:

Activity

  1. added
    type/proposalThe new feature has not been accepted yet but needs to be discussed first.
    on Feb 23, 2017
  2. added this to the milestone on Feb 23, 2017
  3. Lourens-Rich commented on Feb 23, 2017

    @Lourens-Rich

    Very good idea!

  4. bkcsoft commented on Feb 27, 2017

    @bkcsoft
    Contributor

    1.2 in February, 1.3 in April, 1.4 in June, 1.5 in August? should be enough time to implement all that 😄

  5. zellyn commented on Mar 10, 2017

    @zellyn

    If you haven't seen it, fantastic and insightful comment supporting your approach to self-hosting only when ready: https://lobste.rs/s/gokjbo/gitea_1_1_0_released/comments/dg9pwe#c_dg9pwe

  6. bkcsoft commented on Apr 7, 2017

    @bkcsoft
    Contributor

    @lunny Now that I think about it (thanks @zellyn for that link 😂 ) Why do we need oauth-provider, complete webhook support, api-documentation, and a complete API for self-hosting?

    OAuth Consumer is required (it's merged AFAIK) so people can login using github auth.
    Drone only uses push hooks, so why would we need the other?

    As for API, not sure why self-hosting requires that at all TBH :)

  7. strk commented on Apr 7, 2017

    @strk
    Member

    I agree about trimming that list. Earlier self-hosting will very likely help us setting priorities better :)

  8. lunny commented on Apr 7, 2017

    @lunny
    MemberAuthor

    @bkcsoft maybe we can setup a hosted site and have a try.

  9. lunny commented on Apr 7, 2017

    @lunny
    MemberAuthor

    @bkcsoft I updated the issue, do you mean that?

  10. ekozan commented on Aug 31, 2017

    @ekozan

    -> OAuth provider (#27) is not closed

  11. bkcsoft commented on Aug 31, 2017

    @bkcsoft
    Contributor

    @ekozan not closed, but scratched from the list of "things we need"

  12. bkcsoft commented on Sep 14, 2017

    @bkcsoft
    Contributor

    Added "Repository Size Limits" since we don't have unlimited storage on the servers...

    My proposal for limits:

    • 0 Orgs
    • 3 Repos
    • 1GB/repo
  13. lunny commented on Sep 14, 2017

    @lunny
    MemberAuthor

    @bkcsoft Did you mean it will be a public service for anyone?

  14. bkcsoft commented on Sep 14, 2017

    @bkcsoft
    Contributor

    Maybe, maybe not, but if it becomes a public service we can't have it unlimited ;)

  15. stevegt commented on May 5, 2018

    @stevegt
    Contributor

    I think dogfooding is important enough that repo size limits may not need to be in the critical path for self-hosting gitea. In the first few days after migrating to gitea, I've run across several feature omissions that made me think self-hosting will help focus effort on getting those things done. Gitea is already a fantastic, highly usable, high-performance tool -- it's a real shame you aren't using it yourselves. ;-)

    Rather than depend on hard size limits, it might instead be helpful to think about how the self-hosted server is going to be administered, who's going to police bad behavior, and what tools they will want. For instance, contributor forks of the gitea project ought to be supported on gitea's own server. This exposes the risk that a user forks gitea, then pushes warez to their fork. Size limits might help prevent pushing large binaries, but might not help with a list of passwords or credit card numbers. A tool that might help in that case is something that detects alien files by diff line count or rolling hash.

    A nice side-effect of having a diff-size tool available is that the code could be available as an option to run during pushes to flag legitimate commits that should have been broken up into smaller pieces anyway. (Related discussion for ways to do this: #3658 (comment).)

    I'd bet there are a lot of other subtle things that will need to be addressed for public-facing servers. It might make sense to use a separate "public hosting" master issue or milestone to track these things.

  16. 113 remaining items

  17. modified the milestones: 1.16.0, 1.17.0 on Nov 15, 2021
  18. modified the milestones: 1.17.0, 1.18.0 on Jun 8, 2022
  19. modified the milestones: 1.18.0, 1.19.0 on Oct 17, 2022
  20. modified the milestones: 1.19.0, 1.20.0 on Jan 31, 2023
  21. techknowlogick commented on Mar 20, 2023

    @techknowlogick
    Member

    There haven't been many updates on this posted, but I just wanted to say it is being worked on. The alternative export API that Github provides is sadly not working for us, it always returns that it fails to export the data. My guess is that the amount of data we have is too much. If anyone has any contacts at Github who can help us out, please let me know :) My contact email is in my bio.

  22. removed this from the 1.20.0 milestone on Jun 5, 2023
  23. unpinned this issue on Dec 4, 2023
  24. pinned this issue on Dec 4, 2023
  25. unpinned this issue on Mar 23, 2024
  26. reopened this on Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    topic/deploymenttype/proposalThe new feature has not been accepted yet but needs to be discussed first.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      ⌂ 换网址