envsync-secure 0.1.0

Securely share .env files with teammates via Firebase

envsync

Securely share .env files with teammates using encryption and Firebase.

Why this exists

Sharing .env files over Slack or email is a security risk. Git is not an option either. envsync encrypts your secrets locally before they ever leave your machine, pushes the encrypted blob to Firestore, and lets teammates pull and decrypt with a shared key.

Install

pip install envsync

Quickstart

Step 1 - Set up on your machine:

envsync init

You will be asked for a project name and the path to your Firebase service account JSON.

Step 2 - Generate a secret key:

envsync keygen

Copy the key and share it with your teammates securely (see below).

Step 3 - Push your .env to Firestore:

envsync push --key YOUR_KEY

Step 4 - Teammate pulls and decrypts:

envsync pull --key YOUR_KEY

Check your current config:

envsync status

Config reference

envsync stores your config at ~/.envsync/config.toml:

[settings]
project_name = "my-project"
service_account_path = "/absolute/path/to/serviceAccountKey.json"

The secret key is never stored here. You manage and share it yourself.

How to share the key with teammates

Never share the key over Slack, email, or any chat tool. Use a password manager that supports secure sharing, such as 1Password, Bitwarden, or Dashlane. Send the key through the password manager's built-in share feature so it never appears in plaintext in a message thread.

Security rules

• Your .env is encrypted locally before it is sent anywhere
• Firestore only ever holds the encrypted blob, which is useless without the key
• The key is your responsibility to share securely
• Never commit your service account JSON to git

.gitignore warning

Add this to your .gitignore immediately:

.env
serviceAccountKey.json
*.json

The service account JSON gives full access to your Firebase project. Treat it like a password.

License

Copyright (c) 2026 Hillel Ilany Freedman

Permission is hereby granted to use this software freely for personal and commercial use. Copying, redistributing, or republishing this software in whole or in part without explicit written permission from the author is not permitted.