nprasad2077/docs
1
1 Fork 0
mirror of https://gitea.com/gitea/docs.git synced 2026-11-15 06:13:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: correct typo in FAQ regarding Configuration Summary (#436)

Browse Source 
Reviewed-on: https://gitea.com/gitea/docs/pulls/436
Reviewed-by: TheFox0x7 <[email protected]>
Co-authored-by: Nicolas <[email protected]>
Co-committed-by: Nicolas <[email protected]>
This commit is contained in:
Nicolas authored and Lunny Xiao committed 2026-06-13 17:07:13 +00:00
1 parent 88f92b0698
commit 98c4aa4bd0
6 files changed
+6 -6
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/help/faq.md
+1 -1
View File
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
Some package vendors might use "/etc/gitea" to store the config file, while some others don't. Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
You could manually find the config file (app.ini) by checking Gitea's startup logs You could manually find the config file (app.ini) by checking Gitea's startup logs
or reading the Gitea Web's Site Administrator -> Confugiraton Summary. or reading the Gitea Web's Site Administrator -> Configuration Summary.
If you are using some isolated enviroments like container (docker), If you are using some isolated enviroments like container (docker),
the path you see usually is not what it is in the host's filesystem. the path you see usually is not what it is in the host's filesystem.
versioned_docs/version-1.22/help/faq.md
+1 -1
View File
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
Some package vendors might use "/etc/gitea" to store the config file, while some others don't. Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
You could manually find the config file (app.ini) by checking Gitea's startup logs You could manually find the config file (app.ini) by checking Gitea's startup logs
or reading the Gitea Web's Site Administrator -> Confugiraton Summary. or reading the Gitea Web's Site Administrator -> Configuration Summary.
If you are using some isolated enviroments like container (docker), If you are using some isolated enviroments like container (docker),
the path you see usually is not what it is in the host's filesystem. the path you see usually is not what it is in the host's filesystem.
versioned_docs/version-1.23/help/faq.md
+1 -1
View File
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
Some package vendors might use "/etc/gitea" to store the config file, while some others don't. Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
You could manually find the config file (app.ini) by checking Gitea's startup logs You could manually find the config file (app.ini) by checking Gitea's startup logs
or reading the Gitea Web's Site Administrator -> Confugiraton Summary. or reading the Gitea Web's Site Administrator -> Configuration Summary.
If you are using some isolated enviroments like container (docker), If you are using some isolated enviroments like container (docker),
the path you see usually is not what it is in the host's filesystem. the path you see usually is not what it is in the host's filesystem.
versioned_docs/version-1.24/help/faq.md
+1 -1
View File
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
Some package vendors might use "/etc/gitea" to store the config file, while some others don't. Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
You could manually find the config file (app.ini) by checking Gitea's startup logs You could manually find the config file (app.ini) by checking Gitea's startup logs
or reading the Gitea Web's Site Administrator -> Confugiraton Summary. or reading the Gitea Web's Site Administrator -> Configuration Summary.
If you are using some isolated enviroments like container (docker), If you are using some isolated enviroments like container (docker),
the path you see usually is not what it is in the host's filesystem. the path you see usually is not what it is in the host's filesystem.
versioned_docs/version-1.25/help/faq.md
+1 -1
View File
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
Some package vendors might use "/etc/gitea" to store the config file, while some others don't. Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
You could manually find the config file (app.ini) by checking Gitea's startup logs You could manually find the config file (app.ini) by checking Gitea's startup logs
or reading the Gitea Web's Site Administrator -> Confugiraton Summary. or reading the Gitea Web's Site Administrator -> Configuration Summary.
If you are using some isolated enviroments like container (docker), If you are using some isolated enviroments like container (docker),
the path you see usually is not what it is in the host's filesystem. the path you see usually is not what it is in the host's filesystem.
versioned_docs/version-1.26/help/faq.md
+1 -1
View File
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
Some package vendors might use "/etc/gitea" to store the config file, while some others don't. Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
You could manually find the config file (app.ini) by checking Gitea's startup logs You could manually find the config file (app.ini) by checking Gitea's startup logs
or reading the Gitea Web's Site Administrator -> Confugiraton Summary. or reading the Gitea Web's Site Administrator -> Configuration Summary.
If you are using some isolated enviroments like container (docker), If you are using some isolated enviroments like container (docker),
the path you see usually is not what it is in the host's filesystem. the path you see usually is not what it is in the host's filesystem.