mirror of
				https://github.com/go-gitea/gitea
				synced 2025-11-04 13:28:25 +00:00 
			
		
		
		
	
		
			
				
	
	
	
		
			7.0 KiB
		
	
	
	
	
	
	
	
			
		
		
	
	
			7.0 KiB
		
	
	
	
	
	
	
	
date, title, slug, weight, toc, draft, menu
| date | title | slug | weight | toc | draft | menu | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017-01-01T16:00:00+02:00 | Usage: Command Line | command-line | 10 | true | false | 
  | 
Command Line
Usage
gitea [global options] command [command options] [arguments...]
Global options
--help,-h: Show help text and exit. Optional. This can be used with any of the subcommands to see help text for it.--version,-v: Show version and exit. Optional. (example:Gitea version 1.1.0+218-g7b907ed built with: bindata, sqlite).
Commands
web
Starts the server:
- Options:
--port number,-p number: Port number. Optional. (default: 3000). Overrides configuration file.--config path,-c path: Gitea configuration file path. Optional. (default: custom/conf/app.ini).--pid path,-P path: Pidfile path. Optional.
 - Examples:
gitea webgitea web --port 80gitea web --config /etc/gitea.ini --pid /var/run/gitea.pid
 - Notes:
- Gitea should not be run as root. To bind to a port below 1000, you can use setcap on
Linux: 
sudo setcap 'cap_net_bind_service=+ep' /path/to/gitea. This will need to be redone every time you update Gitea. 
 - Gitea should not be run as root. To bind to a port below 1000, you can use setcap on
Linux: 
 
admin
Admin operations:
- Commands:
create-user- Options:
--name value: Username. Required.--password value: Password. Required.--email value: Email. Required.--admin: If provided, this makes the user an admin. Optional.--config path: Gitea configuration file path. Optional. (default: custom/conf/app.ini).
 - Examples:
gitea admin create-user --name myname --password asecurepassword --email me@example.com
 
- Options:
 change-password- Options:
--username value,-u value: Username. Required.--password value,-p value: New password. Required.--config path: Gitea configuration file path. Optional. (default: custom/conf/app.ini).
 - Examples:
gitea admin change-password --username myname --password asecurepassword
 
- Options:
 regenerate- Options:
hooks: Regenerate git-hooks for all repositorieskeys: Regenerate authorized_keys file
 - Examples:
gitea admin regenerate hooksgitea admin regenerate keys
 
- Options:
 auth:list:- Description: lists all external authentication sources that exist
 - Options:
--config path: Gitea configuration file path. Optional. (default: custom/conf/app.ini).
 - Examples:
gitea auth list
 
delete:- Options:
--id: ID of source to be deleted. Required.--config path: Gitea configuration file path. Optional. (default: custom/conf/app.ini).
 - Examples:
gitea auth delete --id 1
 
- Options:
 add-oauth:- Options:
--config path: Gitea configuration file path. Optional. (default: custom/conf/app.ini).--name: Application Name.--provider: OAuth2 Provider.--key: Client ID (Key).--secret: Client Secret.--auto-discover-url: OpenID Connect Auto Discovery URL (only required when using OpenID Connect as provider).--use-custom-urls: Use custom URLs for GitLab/GitHub OAuth endpoints.--custom-auth-url: Use a custom Authorization URL (option for GitLab/GitHub).--custom-token-url: Use a custom Token URL (option for GitLab/GitHub).--custom-profile-url: Use a custom Profile URL (option for GitLab/GitHub).--custom-email-url: Use a custom Email URL (option for GitHub).
 - Examples:
gitea auth add-oauth --name external-github --provider github --key OBTAIN_FROM_SOURCE --secret OBTAIN_FROM_SOURCE
 
- Options:
 update-oauth:- Options:
--id: ID of source to be updated. Required.--config path: Gitea configuration file path. Optional. (default: custom/conf/app.ini).--name: Application Name.--provider: OAuth2 Provider.--key: Client ID (Key).--secret: Client Secret.--auto-discover-url: OpenID Connect Auto Discovery URL (only required when using OpenID Connect as provider).--use-custom-urls: Use custom URLs for GitLab/GitHub OAuth endpoints.--custom-auth-url: Use a custom Authorization URL (option for GitLab/GitHub).--custom-token-url: Use a custom Token URL (option for GitLab/GitHub).--custom-profile-url: Use a custom Profile URL (option for GitLab/GitHub).--custom-email-url: Use a custom Email URL (option for GitHub).
 - Examples:
gitea auth update-oauth --id 1 --name external-github-updated
 
- Options:
 
 
cert
Generates a self-signed SSL certificate. Outputs to cert.pem and key.pem in the current
directory and will overwrite any existing files.
- Options:
--host value: Comma seperated hostnames and ips which this certificate is valid for. Wildcards are supported. Required.--ecdsa-curve value: ECDSA curve to use to generate a key. Optional. Valid options are P224, P256, P384, P521.--rsa-bits value: Size of RSA key to generate. Optional. Ignored if --ecdsa-curve is set. (default: 2048).--start-date value: Creation date. Optional. (format:Jan 1 15:04:05 2011).--duration value: Duration which the certificate is valid for. Optional. (default: 8760h0m0s)--ca: If provided, this cert generates it's own certificate authority. Optional.
 - Examples:
gitea cert --host git.example.com,example.com,www.example.com --ca
 
dump
Dumps all files and databases into a zip file. Outputs into a file like gitea-dump-1482906742.zip
in the current directory.
- Options:
--config path,-c path: Gitea configuration file path. Optional. (default: custom/conf/app.ini).--tempdir path,-t path: Path to the temporary directory used. Optional. (default: /tmp).--verbose,-v: If provided, shows additional details. Optional.
 - Examples:
gitea dumpgitea dump --verbose
 
generate
Generates random values and tokens for usage in configuration file. Useful for generating values for automatic deployments.
- Commands:
secret:- Options:
INTERNAL_TOKEN: Token used for an internal API call authentication.LFS_JWT_SECRET: LFS authentication secret.SECRET_KEY: Global secret key.
 - Examples:
gitea generate secret INTERNAL_TOKENgitea generate secret LFS_JWT_SECRETgitea generate secret SECRET_KEY
 
- Options: