Skip to content
This repository has been archived by the owner on Jul 31, 2023. It is now read-only.

Commit

Permalink
image is available on docker hub
Browse files Browse the repository at this point in the history
  • Loading branch information
grahovam committed Feb 23, 2016
1 parent b8ef172 commit 4e72040
Showing 1 changed file with 2 additions and 5 deletions.
7 changes: 2 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,9 +37,6 @@ and attach it to the User created in Step 2. Replace myBackupBucket with the nam

Step 4. Copy a public gpg key into a folder that can be mount by the docker container later. It is going to be used to encrypt your backup. Write down the Emailadress of the gpg key and don't lose it.


docker build -t backup-gpg-s3 .

Step 5. Run the container

```bash
Expand All @@ -54,7 +51,7 @@ docker run -d \
--env "AWS_ACCESS_KEY_ID=myAWSAccessKey" \
--env "AWS_SECRET_ACCESS_KEY=myAWSSecretAccess" \
--env "AWS_DEFAULT_REGION=eu-central-1" \
backup-gpg-s3
graho/backup-gpg-s3
```

This container is going to perform a backup every day at 4 am. You can define the backup schedule with ```GPG_RECIPIENT```.
Expand Down Expand Up @@ -132,7 +129,7 @@ docker run -it -rm \
--env "AWS_ACCESS_KEY_ID=\\\\" \
--env "AWS_SECRET_ACCESS_KEY=\\\\" \
--env "AWS_DEFAULT_REGION=eu-central-1" \
backup-gpg-s3 bash /restore.sh
graho/backup-gpg-s3 bash /restore.sh
```

You will be asked to enter the name of the backup. If your private gpg key has a password you will be asked for it, too.
Expand Down

0 comments on commit 4e72040

Please sign in to comment.