Omit database dump when doing gitea-dump #9511

Closed
opened 2025-11-02 08:41:18 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @snakers4 on GitHub (Sep 4, 2022).

Feature Description

Gitea dump docs say the following:

Inside the gitea-dump-1482906742.zip file, will be the following:
...
gitea-db.sql - SQL dump of database
gitea-repo.zip - Complete copy of the repository directory.

I use a slightly modified gitea Dockerfile with a local folder as an attached volume and an external database:

        volumes:
            - /home/snakers4/gitea:/data
            - /etc/timezone:/etc/timezone:ro
            - /etc/localtime:/etc/localtime:ro

So, I have a question / feature proposal:

  • Can database dump be omitted during gitea-dump?
  • Can gitea be backed by just stopping it and backing up the database and the /data folder separately?

Screenshots

No response

Originally created by @snakers4 on GitHub (Sep 4, 2022). ### Feature Description Gitea dump docs say the [following](https://docs.gitea.io/en-us/backup-and-restore/#backup-command-dump): > Inside the gitea-dump-1482906742.zip file, will be the following: > ... > gitea-db.sql - SQL dump of database > gitea-repo.zip - Complete copy of the repository directory. I use a slightly modified gitea Dockerfile with a local folder as an attached volume and an external database: ``` volumes: - /home/snakers4/gitea:/data - /etc/timezone:/etc/timezone:ro - /etc/localtime:/etc/localtime:ro ``` So, I have a question / feature proposal: - Can database dump be omitted during `gitea-dump`? - Can gitea be backed by just stopping it and backing up the database and the `/data` folder separately? ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 08:41:18 -06:00
Author
Owner

@JulienPalard commented on GitHub (May 2, 2024):

Looks like a duplicate of: https://github.com/go-gitea/gitea/issues/28720 which has been resolved by @kemzeb adding a --skip-db argument.

But I'm also interested by the idea of "just stopping it and backing up the database and the /data folder separately" answer.

@JulienPalard commented on GitHub (May 2, 2024): Looks like a duplicate of: https://github.com/go-gitea/gitea/issues/28720 which has been resolved by @kemzeb adding a `--skip-db` argument. But I'm also interested by the idea of "just stopping it and backing up the database and the /data folder separately" answer.
Author
Owner

@lunny commented on GitHub (May 3, 2024):

Can database dump be omitted during gitea-dump?

#28720 did that like @JulienPalard said.

Can gitea be backed by just stopping it and backing up the database and the /data folder separately?

Yes for the standard installation from docker.

I think this issue could be closed. Please feel free to reopen it if you have any further problem.

@lunny commented on GitHub (May 3, 2024): > Can database dump be omitted during gitea-dump? #28720 did that like @JulienPalard said. > Can gitea be backed by just stopping it and backing up the database and the /data folder separately? Yes for the standard installation from docker. I think this issue could be closed. Please feel free to reopen it if you have any further problem.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9511