paisa VS cuelm

My attempt at solving the same problem https://paisa.fyi. It builds on top of https://plaintextaccounting.org/ principles and is available as a CLI/Desktop App.

I came across this on hackernews: https://paisa.fyi/

Looks nice. Aside from the fact that the site is under heavy load (hug of death), I’ve been exploring such projects off late myself.

Also, I found https://github.com/ananthakumaran/paisa to be a really clean and well implemented project on similar lines. It already handles a bunch of asset classes familiar to the country I’m residing in which is tempting me to give it a shot sometime soon!

I am building a Web UI called paisa[1] to visualize personal finance data. We currently have very good command line tooling for this (ledger/hledger/beancount). A Web UI will make it even easier to see what's going on with your finances.

I am interested in knowing what are the common problems you face with command line approach that can be solved via a Web UI

[1]: https://github.com/ananthakumaran/paisa

[2]: https://paisa-demo.ananthakumaran.in/

I am working on a self hosted personal finance tool called paisa. It has a rudimentary import page

We've started working on a tool to use CUE to create a single config space across TF, Helm, and other tools in the devops space.

https://github.com/hofstadter-io/cuelm

Our hypothesis is that a unified config space across our industry will bring many benefits.

Our open questions are largely around whether we

(1) replace / alternative

(2) just a skin, still same reconciliation loop from the tools

(3) replace, but support existing modules & charts

Thanks for the share! Very timely

We are in the process of introspecting TF to produce CUE schemas. Maybe this can help us cuetify user TF as well

if you are curious: https://github.com/hofstadter-io/cuelm (it has expanded in scope since inception to include the likes of TF and other areas of e2e CI)