Question 1

How do I set up history-sync with GitHub?

Accepted Answer

First, create a private GitHub repository with SSH key access. Then, clone it locally and set the ZSH_HISTORY_PROJ environment variable to the clone path. Configure your GPG keys and recipients as per the README, and use commands like zhps to push encrypted history.

Question 2

Is history-sync secure for team use?

Accepted Answer

Yes, by using GPG's web of trust with multiple recipients, you can share encrypted history among trusted members. However, key management becomes more complex, and all team members must have Oh My Zsh and the plugin set up.

Question 3

How to handle merge conflicts with history-sync?

Accepted Answer

Since it uses Git, conflicts can occur if multiple machines push changes. You'll need to resolve them manually by decrypting, editing, and re-encrypting the history file, a process not detailed in the README and requires GPG expertise.

Question 4

Can I automate history sync with history-sync?

Accepted Answer

You can add zhsync to a cron job or Zsh hook for periodic syncs. But this requires GPG keys to be available without passphrase prompts, which poses security risks if not managed carefully.

Question 5

What are alternatives to history-sync for Zsh history?

Accepted Answer

Alternatives include atuin for cloud-based sync with search features, or simple scripts using rsync. history-sync is unique for its Git and GPG approach, but atuin might offer more out-of-the-box functionality.

Question 6

Does history-sync work with Bitbucket or other Git hosts?

Accepted Answer

Yes, the README specifies it can use any hosted Git repository like GitHub or Bitbucket, as long as SSH key access is configured and the ZSH_HISTORY_GIT_REMOTE environment variable is set accordingly.

history-sync (wulfgarpro)

What is history-sync (wulfgarpro)?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions