Can I use CLI 2.0 on external machines (like Raspberry Pi)?

Hey XIII ,

Just following up with the answers to your original questions about Connect:

Should the 1password-credentials.json file be permanently saved on my Pi, because it is used in the YAML template?

1password-credentials.json with the standard docker-compose file, should always be there, because it is mounted as a volume. Alternatively, you could copy the file in the containers, instead of mounting it as a volume, and then you'd only need it when starting up Connect.

Is this safe?

I think this doc about https://developer.1password.com/docs/connect/connect-security/ can answer this one.

I'm confused about the pricing: does 1 token for 1 vault count as 1 of the 3 free credits? (I subscribe to 1Password for Families)

The credits represent the number of vaults that are accessed with Secrets Automation.
Here are a couple of examples:

• 3 access tokens that access 1 vault -> 1 credit
• 3 access tokens, 1 for vault A, 2 for vault B -> 2 credits
• 3 access tokens for 3 different vaults -> 3 credits
• 1 access token that can access 3 vaults -> 3 credits
• 2 access tokens, 1 can access vaults A and B, 1 only vault B -> 2 credits
• 2 access tokens, 1 can access vaults A and B, 1 vaults B and C -> 3 credits

What's the best practice for storing the Automation Access Token on the Pi?

I personally always store them as environment variables, only within the session where I make Connect requests (i.e. I never put it in my profile, to have it exported globally). However, I don't think we have ever given exact guidelines towards good practices here, and I've always only used Connect for testing purposes, so ymmv.