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

A new subcommand named doctor to detect all the possible problems #8781

Closed
2 tasks
lunny opened this issue Nov 2, 2019 · 8 comments
Closed
2 tasks

A new subcommand named doctor to detect all the possible problems #8781

lunny opened this issue Nov 2, 2019 · 8 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@lunny
Copy link
Member

lunny commented Nov 2, 2019

A new doctor subcommand could check gitea's running status, it could includes:

  • Repositories file system permissions. It could read app.ini to get running user and check if all the repositories could be read/write by the user.
  • Repositories Hooks script address. It could check if all the repositories hooks script address is current binary's address.

Welcome to add more.
@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Nov 2, 2019
@guillep2k
Copy link
Member

guillep2k commented Nov 2, 2019 •
edited by lunny
Loading

  • Repositories under gitea-repositories that are missing from the database, and the other way around.
  • authorized_keys script address.
  • Assets that are found in data/attachment but are not linked in gitea, and the other way around.
  • Automatically detect all running instances.
  • Search for app.ini; try to figure out its configuration.

@lunny lunny changed the title I think we could create a new subcommand named doctor to detect all the possible problems A new subcommand named doctor to detect all the possible problems Nov 2, 2019
@guillep2k guillep2k mentioned this issue Nov 20, 2019
Merged
@sapk
Copy link
Member

sapk commented Jan 16, 2020

Can you review what functions are already implemented in doctor command to keep progress ?

@sapk
Copy link
Member

sapk commented Jan 16, 2020

This command could include #2762

@lunny
Copy link
Member Author

lunny commented Jan 16, 2020

@sapk I have checked one on @guillep2k 's list.

@sapk
Copy link
Member

sapk commented Jan 29, 2020 •
edited
Loading

It happen many times that users don't find where are some folder/path used by gitea (like the custom folder). Maybe we could dump those information when running doctor command ?
Edit: Nevermind those are visible in the admin ui.

@guillep2k
Copy link
Member

It happen many times that users don't find where are some folder/path used by gitea (like the custom folder). Maybe we could dump those information when running doctor command ?
Edit: Nevermind those are visible in the admin ui.

@sapk I'm sure it won't hurt, anyway.

@guillep2k guillep2k mentioned this issue Jan 30, 2020
Merged
@guillep2k
Copy link
Member

It happen many times that users don't find where are some folder/path used by gitea (like the custom folder). Maybe we could dump those information when running doctor command ?

@sapk #10064 😄

As you've mentioned, the configuration tab in settings is also very useful because oftentimes the users do have Gitea running and they only need to e.g. customize it.

@lunny
Copy link
Member Author

lunny commented Sep 9, 2020

Closed and thanks @guillep2k

@lunny lunny closed this as completed Sep 9, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
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 @sapk @guillep2k