[doc] ./gitea dump doesn't allows to specify backup destination

[vizcay]

I like gitea dump because it allows to backup everything into a single file, but I find it difficult to automate (weekly cron job) because it's doesn't allows to specify the exact destination of the backup (to copy it elsewhere for example).

That leaves us with the (not pretty) option to parse the output to get the zip name.. something like gitea dump --destination /path/to/zip would be great.

Sorry not a go developer, if not I will simply send a PR for this (yeps it's a lame excuse, I know =)

[vizcay]

./gitea dump 2>&1 >/dev/null | awk 'END {print $NF}'
(just in case somebody wonders how to get it)

[lafriks]

I think WIP PR #1637 will implement this?

[vizcay]

@lafriks Not exactly:

   --config FILE, -c FILE   Custom configuration FILE path (default: "custom/conf/app.ini")
   --tempdir PATH, -t PATH  Temporary directory PATH (default: "/tmp")
   --target PATH            Target directory PATH to save backup archive (default: "./")
   --verbose, -v            Show process details
   --db                     Backup the database (default: true)
   --repos                  Backup repositories (default: true)
   --data                   Backup attachments and avatars (default: true)
   --custom                 Backup custom files (default: true)

--target will allow to specify where to land the zip, but still no luck to set the filename.

[bkcsoft]

Should be easy enough to change --target to take a filename instead of a directory :)

[jabouchleih]

Was this functionality removed?

OPTIONS:
--config value, -c value Custom configuration file path (default: "custom/conf/app.ini")
--verbose, -v Show process details
--tempdir value, -t value Temporary dir path (default: "/tmp")
--database value, -d value Specify the database SQL syntax

[vizcay]

@Quinity to be honest IDK, I ended using awk to extract the dump filename but a --target or something similar will be much more appreciated.

[The-King-of-Toasters]

I recently tried tackling this using cron on my debian machine, but I had no luck. However, I found great sucess using a systemd service/timer and setting the WorkingDirectory to wherever you like.

The service file:

[Unit]
Description=Gitea Dump

[Service]
Type=simple
User=git
Group=git
WorkingDirectory=/var/gitea/backup
ExecStart=/usr/local/bin/gitea dump -c /etc/gitea/app.ini
Environment=USER=git HOME=/home/git GITEA_WORK_DIR=/var/lib/gitea

[Install]
WantedBy=multi-user.target

Timer:

[Unit]
Description=Daily Gitea Dump

[Timer]
# See systemd.time(7) for time format
OnCalendar=*-*-* 05:00:00
Persistent=true

[Install]
WantedBy=timers.target

And the output of /var/gitea/backup:

$ ls /var/gitea/backup
gitea-dump-1529562686.zip

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[nodiscc]

--target is not documented in https://docs.gitea.io/en-us/backup-and-restore/