op cli and publishing dotfiles - what config files are safe to publish?

oschrenk
oschrenk
Community Member
edited July 22 in CLI

I am a big fan of having public dotfiles, if only to share my configuration between my machines.

I am also (trying to be) really careful and safe. What files are safe to be published publically when it comes to the op cli?

This is what I currently have (and think in comments

├── config                   // re-created on each machine, don't publish
├── op-daemon.sock  // re-created on each machine, don't publish
├── plugins
│   ├── gh.json           // redundant (in my use case)
│   └── used_items   // safe to publish 
│       └── gh.json      // safe to publish as it only contains references but not the secrets?
└── plugins.sh            // safe to publish, "just" code

Any thoughts?


1Password Version: 1Password for Mac 8.10.36 (81036049)
Extension Version: Not Provided
OS Version: 14.5 (23F79)
Browser: Not Provided