enpass-cli VS ent

Enpass has a CLI client and it's MIT-licensed.

https://github.com/hazcod/enpass-cli

In my opinion, Enpass has the best balance of privacy, open-source, offline-first, etc. It's essentially a proprietary UI over a sqlite/SQLCipher database (fully open source CLI available: https://github.com/hazcod/enpass-cli).

It can - but needn't - be sync'd any number of ways (iCloud, Dropbox, Google Drive, OneDrive, WebDAV), if that's what you like. Because it has WebDAV sync support, you can use it with ownCloud or NextCloud without much fuss, and not have to trust a third party at all.

When this first hit the news I started planning my migration. I settled on Enpass https://www.enpass.io/ . The main client is closed source but the password file is an encrypted SQLite database and is readable by open source tools (written in Go https://github.com/hazcod/enpass-cli).

The UI isn't quite as polished as 1Password but it's pretty good, and more consistent/discoverable IMHO.

For cloud-based, I think BitWarden is the obvious consensus. For local-first, I settled on Enpass. It's closed source and proprietary but the format is decently documented and they provided help in making an open-source database reader https://github.com/hazcod/enpass-cli

Now my passwords are somewhere I control, in a format I can read with open source tools, and sync is done by Dropbox/maestral. It's like being back on classic 1Password but slightly more stable and slightly less polished in the UI.

My open-source implementation of an Enpass command line client could use some love! https://github.com/HazCod/enpass-cli

In this article, we'll delve into the world of concurrency control in Go, specifically focusing on the optimistic locking approach. We'll explore its implementation using Ent ORM to illustrate how to manage data consistency when multiple users interact with the same resource. Keep in mind that this example serves as a simplified illustration, and real-world booking systems involve a many of additional complexities. However, the core concepts presented here provide a solid foundation for understanding optimistic locking in Go applications. Feel free to explore the complete source code in my GitHub repository for a more in-depth look at the implementation.

ent is a fairly recent ORM that uses a code-first approach where you define your schema in Go code. Ent is popular thanks to its ability to handle complex data models and relationships elegantly. It's statically typed, which can help catch errors at compile time. However, the learning curve might be steeper compared to more straightforward ORMs like GORM. It's a good fit for applications where complex data models and type safety are priorities.

If you found this article, than you are probably similar to how I was a few months ago. I started a project in Go that required a SQL backend and I wanted to use any tool that would help me build this backend quickly. I stumbled upon entgo (an ORM for Go) and decided to give it a try.

The ent orm for golang actually does some useful work for you. https://github.com/ent/ent

Backend Database interaction with entgo

You can use entgo.io for ORM stuff, it also has entgql extension that integrated with GQLGen. See more at the document: https://entgo.io/docs/tutorial-todo-gql