-
Updated
Jul 20, 2021 - Go
backup
Here are 3,698 public repositories matching this topic...
-
Updated
Apr 26, 2021 - Shell
-
Updated
Jul 10, 2021 - JavaScript
Currently, the cluster migration docs don't specify that Velero doesn't support restoring into a cluster with a lower K8s version than where the backup was taken. Please add that note under the "Migrating Workloads Across Different Kubernetes Versions" section at the bottom of the doc: https://velero.io/docs/v1.6/migration-case/
Vote on this issue!
This is an invitation to the Velero com
What went wrong?
I'm getting deprecation warnings with openSSL encryption.
[2019/09/05 08:38:52][info] Using Encryptor::OpenSSL to encrypt the archive.
[2019/09/05 08:40:22][warn] Pipeline STDERR Messages:
[2019/09/05 08:40:22][warn] (Note: may be interleaved if multiple commands returned error messages)
[2019/09/05 08:40:22][warn]
[2019/09/05 08:40:22][warn] *** WARNING : depre
The class BackupDestination with function 'write' writes the backup file towards for example S3, but when f.e. S3MultipartUploadException occurs, the flysystem class returns 'false' instead of the exception. The backup is still marked as succesful.
-
Updated
Jul 10, 2021 - Python
-
Updated
Mar 18, 2021 - Python
General information
- App version: v0.8.0
- App source: Google Play
- Android Version: 9.0
Expected result
The activity org.shadowice.flocke.andotp.Activities.PanicResponderActivity should be protected.
andOTP should restrict which applications can launch the Activity.
What does happen instead?
There are two attack scenarios:
- Any application can sta
-
Updated
Jan 26, 2021 - Go
-
Updated
Jun 25, 2021 - Shell
-
Updated
Jun 12, 2021 - Perl
-
Updated
May 20, 2021 - C++
-
Updated
Apr 12, 2021 - PHP
-
Updated
Jun 7, 2021 - Python
-
Updated
Jun 22, 2021 - PHP
-
Updated
Jul 5, 2021 - Python
-
Updated
Jul 23, 2021 - Python
-
Updated
Jul 2, 2021 - Python
-
Updated
Jul 16, 2021 - Go
I am synching my local repo to a Wasabi S3 bucket daily. I am capturing the output from the cron job and have that one sent as an e-mail to myself. The output of the sync-to command is reallly… lengthy and I am actually not interested in that output.
How about adding the --no-progress option to this command, so it only outputs any errors ans not the whole progress?
Improve this page
Add a description, image, and links to the backup topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the backup topic, visit your repo's landing page and select "manage topics."
the borg files cache can be rather large, because it keeps some information about all files that have been processed recently.
lz4 is a very fast compression / decompression algorithm, so we could try to use it to lower the in-memory footprint of the files cache entries.
before implementing this, we should check how big the savings typically are - to determine whether it is worthwhile doing