foster/forgejo-docs
0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-11-22 17:48:39 -05:00
Code Issues Activity

Unify Alpine versions across the repo

Browse source 
This mainly came about because I noticed an inconsistency in the
`docs/user/actions.md` section, where it said a snippet ensures the usage
of _Alpine 3.18_, but the snippet actually obviously said _3.19_.

While I was at it, I just updated all mentions of Alpine I could find to
the current _3.20_.

(cherry picked from commit 681f3a8369)
This commit is contained in:
Oto Šťáva 2024-11-22 10:41:08 +01:00 committed by github-actions[bot]
parent 8be347ebde
commit e936cf9bfb
3 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/admin/actions.md
View file

@ -111,7 +111,7 @@ The default container container image can be overridden by a workflow:
```yaml ```yaml
runs-on: docker runs-on: docker
container: container:
image: alpine:3.18 image: alpine:3.20
``` ```
See the user documentation for `jobs.<job_id>.container` for more information. See the user documentation for `jobs.<job_id>.container` for more information.
@ -119,7 +119,7 @@ See the user documentation for `jobs.<job_id>.container` for more information.
Label examples: Label examples:
- `node20:docker://node:20-bookworm` == `node20:docker://docker.io/node:20-bookworm` defines `node20` to be the `node:20-bookworm` image from hub.docker.com - `node20:docker://node:20-bookworm` == `node20:docker://docker.io/node:20-bookworm` defines `node20` to be the `node:20-bookworm` image from hub.docker.com
- `docker:docker://code.forgejo.org/oci/alpine:3.18` defines `docker` to be the `alpine:3.18` image from https://code.forgejo.org/oci/-/packages/container/alpine/3.18 - `docker:docker://code.forgejo.org/oci/alpine:3.20` defines `docker` to be the `alpine:3.20` image from https://code.forgejo.org/oci/-/packages/container/alpine/3.20
### LXC ### LXC

10
docs/user/actions.md
View file

@ -781,12 +781,12 @@ steps:
### `jobs.<job_id>.container.image` ### `jobs.<job_id>.container.image`
- **Docker or Podman:** - **Docker or Podman:**
If the default image is unsuitable, a job can specify an alternate container image with `container:`, [as shown in this example](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-container/.forgejo/workflows/test.yml). If not specified, the shell defaults to `sh`. For instance the following will ensure the job is run using [Alpine 3.18](https://hub.docker.com/_/alpine/tags?name=3.18). If the default image is unsuitable, a job can specify an alternate container image with `container:`, [as shown in this example](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-container/.forgejo/workflows/test.yml). If not specified, the shell defaults to `sh`. For instance the following will ensure the job is run using [Alpine 3.20](https://hub.docker.com/_/alpine/tags?name=3.20).
```yaml ```yaml
runs-on: docker runs-on: docker
container: container:
image: alpine:3.19 image: alpine:3.20
``` ```
- **LXC:** - **LXC:**
@ -812,7 +812,7 @@ The credentials are the same values that you would provide to the docker login c
```yaml ```yaml
runs-on: docker runs-on: docker
container: container:
image: alpine:3.18 image: alpine:3.20
credentials: credentials:
username: 'root' username: 'root'
password: 'admin1234' password: 'admin1234'
@ -898,7 +898,7 @@ jobs:
test: test:
runs-on: docker runs-on: docker
container: container:
image: alpine:3.19 image: alpine:3.20
steps: steps:
- run: | - run: |
grep Alpine /etc/os-release grep Alpine /etc/os-release
@ -1145,7 +1145,7 @@ test "KEY2=$KEY2" = "KEY2=value2"
- [Local actions](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-local-action/.forgejo) - using an action found in a directory instead of a remote repository. - [Local actions](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-local-action/.forgejo) - using an action found in a directory instead of a remote repository.
- [PostgreSQL service](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-service/.forgejo/workflows/test.yml) - a PostgreSQL service and a connection to display the (empty) list of tables of the default database. - [PostgreSQL service](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-service/.forgejo/workflows/test.yml) - a PostgreSQL service and a connection to display the (empty) list of tables of the default database.
- [Using services](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-service/.forgejo/workflows/test.yml) - illustrates how to configure and use services. - [Using services](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-service/.forgejo/workflows/test.yml) - illustrates how to configure and use services.
- [Choosing the image with `container`](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-container/.forgejo/workflows/test.yml) - replacing the `runs-on: docker` image with the `alpine:3.18` image using `container:`. - [Choosing the image with `container`](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-container/.forgejo/workflows/test.yml) - replacing the `runs-on: docker` image with the `alpine:3.20` image using `container:`.
- [Docker action](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-docker-action/.forgejo/workflows/test.yml) - using a action implemented as a `Dockerfile`. - [Docker action](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-docker-action/.forgejo/workflows/test.yml) - using a action implemented as a `Dockerfile`.
- [`on.pull_request` and `on.pull_request_target` events](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-pull-request/.forgejo/workflows/test.yml). - [`on.pull_request` and `on.pull_request_target` events](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-pull-request/.forgejo/workflows/test.yml).
- [`on.schedule` event](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-cron/.forgejo/workflows/test.yml). - [`on.schedule` event](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-cron/.forgejo/workflows/test.yml).

6
docs/user/packages/alpine.md
View file

@ -55,7 +55,7 @@ PUT https://forgejo.example.com/api/packages/{owner}/alpine/{branch}/{repository
| Parameter | Description | | Parameter | Description |
| ------------ | ------------------------------------------------------------------------------------------------------------------------- | | ------------ | ------------------------------------------------------------------------------------------------------------------------- |
| `owner` | The owner of the package. | | `owner` | The owner of the package. |
| `branch` | The branch may match the release version of the OS, ex: `v3.17`. | | `branch` | The branch may match the release version of the OS, ex: `v3.20`. |
| `repository` | The repository can be used [to group packages](https://wiki.alpinelinux.org/wiki/Repositories) or just `main` or similar. | | `repository` | The repository can be used [to group packages](https://wiki.alpinelinux.org/wiki/Repositories) or just `main` or similar. |
Example request using HTTP Basic authentication: Example request using HTTP Basic authentication:
@ -63,7 +63,7 @@ Example request using HTTP Basic authentication:
```shell ```shell
curl --user your_username:your_password_or_token \ curl --user your_username:your_password_or_token \
--upload-file path/to/file.apk \ --upload-file path/to/file.apk \
https://forgejo.example.com/api/packages/testuser/alpine/v3.17/main https://forgejo.example.com/api/packages/testuser/alpine/v3.20/main
``` ```
If you are using 2FA or OAuth use a [personal access token](../../api-usage/#authentication) instead of the password. If you are using 2FA or OAuth use a [personal access token](../../api-usage/#authentication) instead of the password.
@ -98,7 +98,7 @@ Example request using HTTP Basic authentication:
```shell ```shell
curl --user your_username:your_token_or_password -X DELETE \ curl --user your_username:your_token_or_password -X DELETE \
https://forgejo.example.com/api/packages/testuser/alpine/v3.17/main/test-package-1.0.0.apk https://forgejo.example.com/api/packages/testuser/alpine/v3.20/main/test-package-1.0.0.apk
``` ```
The server responds with the following HTTP Status codes. The server responds with the following HTTP Status codes.