3 ms·

Thanks for the suggestions! I read your code and the support of images is awesome. I would not assume everyone has sqlite but this can be done optionally with

Thanks for the suggestions! I read your code and the support of images is awesome. I would not assume everyone has sqlite but this can be done optionally with a plugin. Will consider writing a demo for this. Using XDG directories and system secrets sounds a lot better than what I did. I will learn how to use them and try to integrate them with my code!

ComputerGuru 2y ago
Shameless plug: we maintain a cross-platform/cross-language secrets store (with cli tooling available) to portably read and wrire secrets (but it doesn’t use the OS facilities for encryption). Linking to the rust implementation because it’s the fastest and most easily portable: https://github.com/neosmart/securestore-rs https://github.com/neosmart/securestore-rs
e12e 2y ago
> I would not assume everyone has sqlite but this can be done optionally with a plugin. Will consider writing a demo for this. Used to be everyone used BerkleyDB or some similar key-value store - for a great many usecases SQLite is just pragmatically better. And it's arguably less exotic than perl. You should of course do what want - but "just use SQLite" is pretty solid advice when dealing with structured data - and almost certainly better than "smart" text file.
- simonmysun 2y ago
  I can't deny the benefits. But in my mind, this is not what ell should take care of. It doesn't intend to store anything whether in a text file or any other format. It should however provide the posibilities for users to store them in any way they like.
  - e12e 2y ago
    Fair enough. I seem to recall a project for keeping infinite bash history that did leverage SQLite - interfacing with such a project might be more interesting. I was more thinking from gp comment that the project might store context or history in its own files - and then SQLite might be a good fit.
    - bomewish 2y ago
      You may be thinking of McFly —- it’s very good.
    - llimllib 2y ago
      Atuin! https://atuin.sh/ https://atuin.sh/
      - simonmysun 2y ago
        This looks nice! Thanks for mentioning it. I should definitely install this on my servers.

ComputerGuru 2y ago

Shameless plug: we maintain a cross-platform/cross-language secrets store (with cli tooling available) to portably read and wrire secrets (but it doesn’t use the OS facilities for encryption). Linking to the rust implementation because it’s the fastest and most easily portable: https://github.com/neosmart/securestore-rs https://github.com/neosmart/securestore-rs

e12e 2y ago

> I would not assume everyone has sqlite but this can be done optionally with a plugin. Will consider writing a demo for this. Used to be everyone used BerkleyDB or some similar key-value store - for a great many usecases SQLite is just pragmatically better. And it's arguably less exotic than perl. You should of course do what want - but "just use SQLite" is pretty solid advice when dealing with structured data - and almost certainly better than "smart" text file.

simonmysun 2y ago
I can't deny the benefits. But in my mind, this is not what ell should take care of. It doesn't intend to store anything whether in a text file or any other format. It should however provide the posibilities for users to store them in any way they like.
- e12e 2y ago
  Fair enough. I seem to recall a project for keeping infinite bash history that did leverage SQLite - interfacing with such a project might be more interesting. I was more thinking from gp comment that the project might store context or history in its own files - and then SQLite might be a good fit.
  - bomewish 2y ago
    You may be thinking of McFly —- it’s very good.
  - llimllib 2y ago
    Atuin! https://atuin.sh/ https://atuin.sh/
    - simonmysun 2y ago
      This looks nice! Thanks for mentioning it. I should definitely install this on my servers.