gitea/gitea-docs
1
0
Fork 0
mirror of https://gitea.com/gitea/docs.git synced 2026-07-22 02:37:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore(docker-compose): remove obsolete version parament & remove useless default external=false (#288)

Browse Source 
- Removed deprecated `version` key from docker-compose.yaml
- Cleaned up unnecessary `external: false` declarations for networks/volumes

Signed-off-by: Snowball_233 <snowballxueqiu@noreply.gitea.com>

Reviewed-on: https://gitea.com/gitea/docs/pulls/288
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com>
Co-authored-by: Snowball_233 <snowballxueqiu@noreply.gitea.com>
Co-committed-by: Snowball_233 <snowballxueqiu@noreply.gitea.com>
This commit is contained in:
Snowball_233
2025-10-30 14:07:06 +00:00
committed by techknowlogick
parent f954c6e7b8
commit d5eac4f23d
1 changed files with 0 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
versioned_docs/version-1.24/installation/with-docker.md
View File

@@ -26,11 +26,8 @@ If you don't give the volume correct permissions, the container may not start.
For a stable release you can use `:latest`, `:1` or specify a certain release like `:@dockerVersion@`, but if you'd like to use the latest development version of Gitea then you could use the `:nightly` tag. If you'd like to run the latest commit from a release branch you can use the `:1.x-nightly` tag, where x is the minor version of Gitea. (e.g. `:1.16-nightly`) For a stable release you can use `:latest`, `:1` or specify a certain release like `:@dockerVersion@`, but if you'd like to use the latest development version of Gitea then you could use the `:nightly` tag. If you'd like to run the latest commit from a release branch you can use the `:1.x-nightly` tag, where x is the minor version of Gitea. (e.g. `:1.16-nightly`)
```yaml ```yaml
version: "3"
networks: networks:
gitea: gitea:
external: false
services: services:
server: server:
@@ -58,11 +55,8 @@ the port section. It's common to just change the host port and keep the ports wi
the container like they are. the container like they are.
```diff ```diff
version: "3"
networks: networks:
gitea: gitea:
external: false
services: services:
server: server:
@@ -93,11 +87,8 @@ To start Gitea in combination with a MySQL database, apply these changes to the
`docker-compose.yml` file created above. `docker-compose.yml` file created above.
```diff ```diff
version: "3"
networks: networks:
gitea: gitea:
external: false
services: services:
server: server:
@@ -144,11 +135,8 @@ To start Gitea in combination with a PostgreSQL database, apply these changes to
the `docker-compose.yml` file created above. the `docker-compose.yml` file created above.
```diff ```diff
version: "3"
networks: networks:
gitea: gitea:
external: false
services: services:
server: server:
@@ -196,11 +184,8 @@ create the required volume. You don't need to worry about permissions with
named volumes; Docker will deal with that automatically. named volumes; Docker will deal with that automatically.
```diff ```diff
version: "3"
networks: networks:
gitea: gitea:
external: false
+volumes: +volumes:
+ gitea: + gitea: