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

Create git-daemon-export-ok file when creating public repositories #15521

Closed
2 of 7 tasks
holtrop opened this issue Apr 16, 2021 · 2 comments · Fixed by #16508
Closed
2 of 7 tasks

Create git-daemon-export-ok file when creating public repositories #15521

holtrop opened this issue Apr 16, 2021 · 2 comments · Fixed by #16508
Labels
type/enhancement An improvement of existing functionality

Comments

@holtrop
Copy link

holtrop commented Apr 16, 2021

  • Gitea version (or commit ref): 1.14.1 (downloaded from web site, running via systemd service)
  • Git version: 2.25.1
  • Operating system: Ubuntu 20.04.2 LTS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • N/A - try.gitea.io appears to not have the git-daemon port open and I cannot tell if it created the git-daemon-export-ok file without that

Description

gitea appears to have support to create the git-daemon-export-ok file when the repository is changed from private to public (done in the updateRepository() function). However, gitea does not create this file when creating a repository (either via New or Migrate options).

I can get gitea to create the git-daemon-export-ok file as I desire after creating a new repository by changing it from public to private, saving the settings, and then changing it from private back to public.

gitea should create the git-daemon-export-ok file when creating a repository if it is set to public visibility to match what is done when changing from private to public.

@noerw noerw added the type/enhancement An improvement of existing functionality label May 16, 2021
@stale
Copy link

stale bot commented Jul 21, 2021

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Jul 21, 2021
@zeripath
Copy link
Contributor

So there are a number of issues here - for a start we need to only create these files only when the repository is actually publicly viewable so the current code is likely incorrect too.

@stale stale bot removed the issue/stale label Jul 21, 2021
zeripath added a commit to zeripath/gitea that referenced this issue Jul 21, 2021
Somewhere along the line the creation of git-daemon-export-ok
files disappeared but the updating of these files when
repo visibility changes remained. The problem is that the
current state will create files even when the org or user
is private.

This PR restores creation correctly.

Fix go-gitea#15521

Signed-off-by: Andrew Thornton <[email protected]>
zeripath added a commit that referenced this issue Jul 22, 2021
Somewhere along the line the creation of git-daemon-export-ok
files disappeared but the updating of these files when
repo visibility changes remained. The problem is that the
current state will create files even when the org or user
is private.

This PR restores creation correctly.

Fix #15521

Signed-off-by: Andrew Thornton <[email protected]>
zeripath added a commit to zeripath/gitea that referenced this issue Jul 22, 2021
Backport go-gitea#16508

Somewhere along the line the creation of git-daemon-export-ok
files disappeared but the updating of these files when
repo visibility changes remained. The problem is that the
current state will create files even when the org or user
is private.

This PR restores creation correctly.

Fix go-gitea#15521

Signed-off-by: Andrew Thornton <[email protected]>
6543 pushed a commit that referenced this issue Jul 22, 2021
Backport #16508

Somewhere along the line the creation of git-daemon-export-ok
files disappeared but the updating of these files when
repo visibility changes remained. The problem is that the
current state will create files even when the org or user
is private.

This PR restores creation correctly.

Fix #15521

Signed-off-by: Andrew Thornton <[email protected]>
AbdulrhmnGhanem pushed a commit to kitspace/gitea that referenced this issue Aug 10, 2021
Somewhere along the line the creation of git-daemon-export-ok
files disappeared but the updating of these files when
repo visibility changes remained. The problem is that the
current state will create files even when the org or user
is private.

This PR restores creation correctly.

Fix go-gitea#15521

Signed-off-by: Andrew Thornton <[email protected]>
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants