Frequently Asked Questions

bwsf is a command that saves managed files (.env*, *.tfvars, *.tfvars.json) to Bitwarden.

Therefore, a Bitwarden account is required to use it.

Of course. bwsf supports self-hosted Bitwarden.

Unfortunately, not at this time. We're actively working on it.

Currently, only macOS/Linux is supported.

bwsf itself is a command installed on individual development machines.

However, it uses Bitwarden as the backend for storing managed files.

Bitwarden allows you to set detailed user permissions, so by configuring users on the Bitwarden side, you can securely manage those files among multiple users.

Bitwarden has several proprietary formats for storing sensitive information.

Among these, bwsf uses a format called "Secure Note".

The Secure Note title is the project name, and the content is stored in JSON format.

Yes, you can. For example:

• .env
• .env.local
• .env.staging
• .env.production
• terraform.tfvars

These managed files are saved all at once.

However, files with .example in the filename are NOT saved.

For example:

• .env ← Save this
• .env.production ← Don't want to save this

Unfortunately, this feature has not been implemented yet.

Yes, if you can visually edit JSON files.

However, if you're developing with multiple members, be careful as unintended pushes from other members may overwrite your changes, or incorrect pulls may occur.

The development team does not officially recommend this.

Yes. From v0.15.0, bwsf manages files ending in .tfvars or .tfvars.json the same way as .env* files (push / pull / list / clean).

Names that contain .example are excluded, just like .env.example.

Please do this on the bw command side. bwsf itself does not have login/logout functionality.