ad-on-is / resticity Goto Github PK

I have set pruning rules up for all my repos and a schedule to run it manually. When i run it, I get this in the docker log

resticity  | 2024/03/19 15:43:15 DEBU Running job manually id=0c11b071-92e1-4daf-afd2-bc5e72ed9a5e
resticity  | 2024/03/19 15:43:15 DEBU before job run id=0c11b071-92e1-4daf-afd2-bc5e72ed9a5e
resticity  | 2024/03/19 15:43:15 DEBU Setting forced running job id=0c11b071-92e1-4daf-afd2-bc5e72ed9a5e
resticity  | 2024/03/19 15:43:15 INFO core repo=s3:xxx/xxx cmd=[unlock]
resticity  | 2024/03/19 15:43:17 INFO core repo=s3:xxx/xxx cmd="[forget --prune --keep-daily 7 --keep-weekly 8 --keep-monthly 10]"
resticity  | 2024/03/19 15:43:17 ERRO executing restic command err="context canceled"
resticity  | 2024/03/19 15:43:17 DEBU after job run res=success id=0c11b071-92e1-4daf-afd2-bc5e72ed9a5e

I know that this prune should delete some snapshots and I can verify that it does not. The UI will also show it as having run succesfully, even though it didnt
I have no idea, what the error "context canceled" means here, so I am not sure what other info to provide. Please let me know if you need anything else.

I setup the app in a docker container, successfully added a repository and a backup, ran the backup, setup pruning rules and pruned the repo. Still there is no text at all on the log page

I am not sure what is supposed to be here, but it would be nice to have a bit more detailed output from restic somewhere, instead of just the green checkmark from the schedules

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x816a55]

goroutine 6 [running]:
github.com/ad-on-is/resticity/internal.runHub()
/build/internal/server.go:64 +0x335
created by github.com/ad-on-is/resticity/internal.RunServer in goroutine 1
/build/internal/server.go:208 +0x1b0

I do not really know how, but sometimes the GUI/server fails. I am running the docker image. I must restart the container.

Is there a way to add an SFTP repo?

I mostly run my backups to Wasabi, but I also have a storage VPS at HostHatch that I like to utilize (currently backing up my Nextcloud server there). Currently running SFTPGO on that server as an endpoint for my NAS to back up to.

I set up a docker-compose.yml, according to the readme

services:                                                                                                                                                                                                    
  resticity:                                                                                                                                                                                                 
    image:   ghcr.io/ad-on-is/resticity/resticity
# Everything else shouldnt really matter

When i try to start it, i get this:

❯ docker compose up
[+] Running 1/1
 ✘ resticity Error                                                                                                                                                                                             0.4s 
Error response from daemon: Head "https://ghcr.io/v2/ad-on-is/resticity/resticity/manifests/latest": unauthorized

So I tried again with an authenticated connection, but that doesnt help either

❯ docker compose up
[+] Running 1/1
 ✘ resticity Error                                                                                                                                                                                             0.7s 
Error response from daemon: denied

I use a lot of gitops, and would love to add the config.json file to my repo for easy backup/restore. Unfortunately, config.json currently contains passwords and api keys in plain text. It goes without saying that it would be a disaster to commit the file to git.

There are any number of ways to improve this issue, but the simplest would probably be to just have a separate secrets file kept in the same directory as config.jason. The secrets file could be added to .gitignore, and config.json could be committed to git without issue.

Finally a good looking Restic GUI!

Thank you.

Installed on Arch, but when attempting to connect to my existing repository, it would crash out after connection in repositories

Looking at the logs, it appears it was trying to save to ~/.config/resticity/config.json which didn't get created on install or first run. Creating the directory and touching the json file fixed the issue.

Hi,
A feature request. Make it work in total portable mode on Windows. Have all executables and configurations in a single folder and/or subfolders.
I want to run this from a portable USB drive.

Regards
M

Discussion moved from lemmy