Updates to doc (#24757)
## Misspelling fixes to: - docs/content/doc/administration/config-cheat-sheet.en-us.md - docs/content/doc/installation/from-source.en-us.md - docs/content/doc/usage/packages/cargo.en-us.md - docs/content/doc/usage/packages/storage.en-us.md --------- Co-authored-by: delvh <dev.lh@web.de>
This commit is contained in:
parent
473dee7c7a
commit
9fb0945a09
4 changed files with 5 additions and 5 deletions
|
@ -220,7 +220,7 @@ The following configuration set `Content-Type: application/vnd.android.package-a
|
||||||
- `SHOW_USER_EMAIL`: **true**: Whether the email of the user should be shown in the Explore Users page.
|
- `SHOW_USER_EMAIL`: **true**: Whether the email of the user should be shown in the Explore Users page.
|
||||||
- `THEMES`: **auto,gitea,arc-green**: All available themes. Allow users select personalized themes.
|
- `THEMES`: **auto,gitea,arc-green**: All available themes. Allow users select personalized themes.
|
||||||
regardless of the value of `DEFAULT_THEME`.
|
regardless of the value of `DEFAULT_THEME`.
|
||||||
- `THEME_COLOR_META_TAG`: **\<empty\>**: Value of `theme-color` meta tag, used by some mobile browers for chrome and out-of-viewport areas. Default is unset which uses body color.
|
- `THEME_COLOR_META_TAG`: **\<empty\>**: Value of `theme-color` meta tag, used by some mobile browsers for chrome and out-of-viewport areas. Default is unset which uses body color.
|
||||||
- `MAX_DISPLAY_FILE_SIZE`: **8388608**: Max size of files to be displayed (default is 8MiB)
|
- `MAX_DISPLAY_FILE_SIZE`: **8388608**: Max size of files to be displayed (default is 8MiB)
|
||||||
- `REACTIONS`: All available reactions users can choose on issues/prs and comments
|
- `REACTIONS`: All available reactions users can choose on issues/prs and comments
|
||||||
Values can be emoji alias (:smile:) or a unicode emoji.
|
Values can be emoji alias (:smile:) or a unicode emoji.
|
||||||
|
|
|
@ -201,7 +201,7 @@ This can be combined with `CC`, `GOOS`, and `GOARCH` as above.
|
||||||
A script to enable bash-completion can be found at [`contrib/autocompletion/bash_autocomplete`](https://raw.githubusercontent.com/go-gitea/gitea/main/contrib/autocompletion/bash_autocomplete). This should be altered as appropriate and can be `source` in your `.bashrc`
|
A script to enable bash-completion can be found at [`contrib/autocompletion/bash_autocomplete`](https://raw.githubusercontent.com/go-gitea/gitea/main/contrib/autocompletion/bash_autocomplete). This should be altered as appropriate and can be `source` in your `.bashrc`
|
||||||
or copied as `/usr/share/bash-completion/completions/gitea`.
|
or copied as `/usr/share/bash-completion/completions/gitea`.
|
||||||
|
|
||||||
Similary a script for zsh-completion can be found at [`contrib/autocompletion/zsh_autocomplete`](https://raw.githubusercontent.com/go-gitea/gitea/main/contrib/autocompletion/zsh_autocomplete). This can be copied to `/usr/share/zsh/_gitea` or sourced within your
|
Similarly, a script for zsh-completion can be found at [`contrib/autocompletion/zsh_autocomplete`](https://raw.githubusercontent.com/go-gitea/gitea/main/contrib/autocompletion/zsh_autocomplete). This can be copied to `/usr/share/zsh/_gitea` or sourced within your
|
||||||
`.zshrc`.
|
`.zshrc`.
|
||||||
|
|
||||||
YMMV and these scripts may need further improvement.
|
YMMV and these scripts may need further improvement.
|
||||||
|
|
|
@ -25,13 +25,13 @@ Publish [Cargo](https://doc.rust-lang.org/stable/cargo/) packages for your user
|
||||||
|
|
||||||
To work with the Cargo package registry, you need [Rust and Cargo](https://www.rust-lang.org/tools/install).
|
To work with the Cargo package registry, you need [Rust and Cargo](https://www.rust-lang.org/tools/install).
|
||||||
|
|
||||||
Cargo stores informations about the available packages in a package index stored in a git repository.
|
Cargo stores information about the available packages in a package index stored in a git repository.
|
||||||
This repository is needed to work with the registry.
|
This repository is needed to work with the registry.
|
||||||
The following section describes how to create it.
|
The following section describes how to create it.
|
||||||
|
|
||||||
## Index Repository
|
## Index Repository
|
||||||
|
|
||||||
Cargo stores informations about the available packages in a package index stored in a git repository.
|
Cargo stores information about the available packages in a package index stored in a git repository.
|
||||||
In Gitea this repository has the special name `_cargo-index`.
|
In Gitea this repository has the special name `_cargo-index`.
|
||||||
After a package was uploaded, its metadata is automatically written to the index.
|
After a package was uploaded, its metadata is automatically written to the index.
|
||||||
The content of this repository should not be manually modified.
|
The content of this repository should not be manually modified.
|
||||||
|
|
|
@ -28,7 +28,7 @@ If two identical files are uploaded only one blob is saved on the filesystem.
|
||||||
This ensures no space is wasted for duplicated files.
|
This ensures no space is wasted for duplicated files.
|
||||||
|
|
||||||
If two packages are uploaded with identical files, both packages will display the same size but on the filesystem they require only half of the size.
|
If two packages are uploaded with identical files, both packages will display the same size but on the filesystem they require only half of the size.
|
||||||
Whenever a package gets deleted only the references to the underlaying blobs are removed.
|
Whenever a package gets deleted, only the references to the underlying blobs are removed.
|
||||||
The blobs get not removed at this moment, so they still require space on the filesystem.
|
The blobs get not removed at this moment, so they still require space on the filesystem.
|
||||||
When a new package gets uploaded the existing blobs may get referenced again.
|
When a new package gets uploaded the existing blobs may get referenced again.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue