1password-linux-to-bitwarden
chezmoi
Our great sponsors
1password-linux-to-bitwarden | chezmoi | |
---|---|---|
5 | 59 | |
36 | 11,639 | |
- | - | |
0.0 | 9.7 | |
over 2 years ago | 2 days ago | |
Go | Go | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
1password-linux-to-bitwarden
-
1Password Has Raised $620M
They have been doing some pretty unfriendly moves towards their long-term customers, like making sure the new 1Password cannot be used without 'the cloud' like the old one could be.
I have no doubt raising more VC money will only accelerate such trends.
In fact I've decided to move off of 1Password to BitWarden, since at least one can realistically self-host it. That being said, it's not exactly easy to migrate from the latest 1Password so I wrote my own little utility to do it[1].
I think we need more competition to VC backed products in general, just imagine what would happen if the building blocks of say a GNU/Linux system we take for granted today would've been built with the mindset that investors are going to want a return on their investment.
I am not saying there's anything wrong with that in principle, but am not sure I want to surrender my passwords to these kinds of incentives.
1 - https://github.com/MatejLach/1password-linux-to-bitwarden
-
New version of 1Password means no way to import 1Password data into Bitwarden
By looking at the decoder of the tool linked in this post, it's just a zip that contains .data files, which are JSON. Still, hiding known file formats (.zip, .json) behind some obscure names (.1pux and .data) does look like a shady pattern to me.
-
1Password .pux file
There are compiled version available: 1.0 - initial binary release
chezmoi
- Securely manage your dot files
-
Ask HN: Did macOS Sonoma break your iCloud setup?
> A warning, not an admonishment: Use Apple services in a novel or unsupported manner and you're asking for trouble.
+1
I've always had sync issues with iCloud Drive when storing developer projects and related things there. It ends up stuck or confused or conflicted but tries to resolve the merge conflicts opaquely and it's hard to know there's a problem in real time vs until later when you find something broken. I keep all dev things out of iCloud after getting burned by this enough times over the years.
To OP: Consider a repo dotfiles setup like using Chezmoi or similar. Transitioning to it was less friction than I expected and the only downside really is having to remember to commit changes across devices.
-
Russ Cox: Go Testing by Example
chezmoi (<https://chezmoi.io> or <https://github.com/twpayne/chezmoi>) has a couple dozen txtar tests. They are both amazing and completely frustrating to use, but I don't think that there would be a better way to test most of what chezmoi does without them.
Tom Payne (the creator and primary developer of chezmoi) has added some extra commands to the txtar context which makes things easier for certain classes of testing.
-
Fake recruiter Lazarus lured aerospace employee with trojanized coding challenge
Thanks, I never heard of it before and it looks really interesting.
However, it seems that it does not cover all of my needs: https://github.com/twpayne/chezmoi/discussions/1510#discussi...
-
Sharing neovim settup
once i need a more complex solution (eg. for machine specific stuff), i'll probably switch to chezmoi which has more features and native windows support
-
I want to mess around with my config files. What is the best way for me to be able to go back and forth between my normal config and my test config?
I’ve been using chezmoi, which uses git, to manage my dot files and have different branches for these types of experiments.
-
Fulfilling a reader's request for my “dot files”
https://chezmoi.io is a dotfile manager that is runs on multiple OSes (including Windows) while handling differences from machine to machine, allows you to store your secrets in your password manager (so you don't have to store secrets in your dotfile repo), and it even supports the NO_COLOR environment variable. Check it out! Disclaimer: I'm the author.
There's a comprehensive list of the most popular dotfile managers at https://dotfiles.github.io/utilities/.
-
Chezmoi: ignore files and subdirectories
/autoload/ **/autoload//* /plugged/ **/plugged//* */yankring_history.txt ``` Discussion
-
What "nice-to-have" CLI tools do you know?
chezmoi
-
Setup a backup system if you haven’t done it yet
Checkout yadm or chezmoi. They work great.
What are some alternatives?
MacPass - A native macOS KeePass client
GNU Stow - GNU Stow - mirror of savannah git repository occasionally with more bleeding-edge branches
onepassword-operator - The 1Password Connect Kubernetes Operator provides the ability to integrate Kubernetes Secrets with 1Password. The operator also handles autorestarting deployments when 1Password items are updated.
yadm - Yet Another Dotfiles Manager
vaultwarden - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
infrastructure - The infrastructure monorepo for the Rocky Linux project. This project will be archived/deprecated in the future.
dotbot - A tool that bootstraps your dotfiles ⚡️
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
mackup - Keep your application settings in sync (OS X/Linux)
portwarden - Create Encrypted Backups of Your Bitwarden Vault with Attachments
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.