Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to "git-crypt" #114

Merged
merged 5 commits into from
Sep 8, 2018
Merged

Conversation

arcticicestudio
Copy link
Owner

Closes #113

The migration was successful and the encryption has been validated by locking and undlocking the repository: git-crypt lock and git-crypt unlock.

1. Deleted the custom `git-diff-igloocrypt` script
2. Removed the custom `[diff "igloocrypt"]` section from the
   `gitconfig` file
3. Removed the custom filter "igloocrypt" from the `gitconfig` file
4. Updated the `filter` and `diff` custom global Git attributes handler
   for all `*.igloocrypt` files to the new `git-crypt` setup

GH-113
1. Decrypted all `*.igloocrypt` files and backuped them up outside the
   repository
2. Deleted all `*.igloocrypt` files within the repository

GH-113
1. Initialized `git-crypt` for the repository: `git-crypt init`
   (default key)
2. Added the main Arctic Ice Studio GPG key:
   `git-crypt add-gpg-user -n <ID>`
   (`-n` flag prevents automatic commit of generated files)

GH-113
1. Unlocked the repository: `git-crypt unlock`
2. Added all backed up `*.igloocrypt` files back into the repository
3. Ensured all `*.igloocrypt` are tracked to be encryped:
   `git-crypt status`

After this commit the encryption can be validated to by locking the
repository again: `git-crypt lock`

GH-113
@arcticicestudio arcticicestudio added this to the 0.1.0 milestone Sep 8, 2018
@arcticicestudio arcticicestudio merged commit 4bb0d48 into develop Sep 8, 2018
@arcticicestudio arcticicestudio deleted the feature/gh-113-migrate-to-git-crypt branch September 8, 2018 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant